rfc4027.Domain Name System Media Types

合集下载

常见的请求状态码

常见的请求状态码

常见的请求状态码在HTTP协议中,请求状态码用于指示服务器对请求的处理结果。

以下是常见的请求状态码及其含义:1. 200 OK:表示服务器已成功处理请求。

2. 201 Created:表示请求已成功并且服务器已创建了新资源。

3. 202 Accepted:表示服务器已接受请求,但尚未处理完成。

4. 204 No Content:表示服务器已成功处理请求,但没有返回任何内容。

5. 400 Bad Request:表示客户端发送的请求存在语法错误或无法理解。

6. 401 Unauthorized:表示请求需要用户身份验证。

7. 403 Forbidden:表示服务器拒绝了客户端的请求。

8. 404 Not Found:表示请求的资源不存在。

9. 405 Method Not Allowed:表示请求方法不被允许。

10. 408 Request Timeout:表示服务器等待客户端发送的请求时间过长。

11. 429 Too Many Requests:表示客户端发送的请求过多,超出了服务器的处理能力。

12. 500 Internal Server Error:表示服务器内部错误,无法完成请求。

13. 502 Bad Gateway:表示服务器作为网关或代理,从上游服务器接收到无效响应。

14. 503 Service Unavailable:表示服务器暂时无法处理请求,通常是由于过载或维护等原因。

15. 504 Gateway Timeout:表示服务器作为网关或代理,等待上游服务器响应超时。

这些状态码帮助客户端了解服务器对其请求的处理结果,使得网络通信更加可靠和健壮。

IIS常见错误代码

IIS常见错误代码

IIS常见错误代码IIS introductionWhen a user attempts to file transfer protocol (FTP) access via HTTP or a running Internet information services (IIS) of the content on the server, IIS the request returns a said the state of the digital code. The status code is logged in the IIS log and may also be displayed on the Web browser or FTP client. The status code can indicate whether the specific request has been successful and can also reveal the exact cause of the request failure.By default, IIS puts its log files in the Windows \ \ System32 \ \ Logfiles folder. Each WWW site and FTP site has a separate directory under that directory. By default, log files are created in these directories each day, and the log files are named (for example, exYYMMDD. Log).HTTP code1x-information tip: these state codes represent temporary responses. The client should be ready to receive one or more 1xx responses before receiving the regular response.100 -101-switching protocol2xx - success: this status code indicates that the server successfully accepts the client request.200 - determines the status code that indicates that IIS has successfully processed the request201 - has been created202 - accepted203-non-authoritative information204 - nothing205 - reset content206 - part of it3xx - redirect: the client browser must do more to implement the request. For example, the browser might have to request a different page on the server or repeat the request through the proxy server.300 - multiple options301 - has been removed forever302 - the object has been found and moved303 - see other terms304 - the document that does not modify the client request is in the client cache, and the document has not been modified since the cache. The client USES the cached copy of the documentwithout downloading the document from the server.305 - use the agent306 - this code has been retained but not used307 - temporary redirects4xx - client error: error occurred, client problem. For example, the client request does not exist and the guest does not provide valid authentication information.400-error request401 - access is rejectedIIS defines a number of different 401 errors that specify more specific error reasons. These specific error codes are displayed in the browser, but not in the IIS log:401.1-login failed login attempts, possibly because the user name or password is invalid.The 401.2-server configuration failed to login3, 401.3 - there is an NTFS permission problem because of the limitation of the ACL to the resource. This error may occur even if you have the appropriate permissions for the file you are trying to access. To solve this problem, see the corresponding article in the Microsoft knowledge base: 187506 List of NTFS Permissions Required for IIS Site to Work (the List of NTFSPermissions Required for the IIS Site Work)401.4 - filter authorization failedThe 401.5-isapi/CGI application authorization failed401.7 - access is rejected by the URL authorization policy on the Web server403 - no accessIIS defines a number of different 403 errors, which specify more specific error reasons, see 403.x code404 - not foundThe reason for this error is that the file you are trying to access has been removed or removed. This error occurs when the URLScan tool is installed to try to access files with a limited extension. In this case, the name "Rejected by URLScan" appears in the log file item of the request.404.0 - no files or directories are found404.1 - you can't access the Web site on the requested portThe 404.2-web service extension locking policy prevents this request4, 404.The 3-mime mapping policy prevents this request405 - the HTTP predicate that is used for accessing this page is not allowed (the method is not allowed)406 - the client browser does not accept the MIME type of the requested page407 - requires agent authentication412-premise failure413 - the request entity is too large414 - the request URI is too long415-unsupported media types416 - the scope of the request cannot be satisfied417 - execution failure423 - lock error5xx - server error: the server cannot complete the request because of error500-internal server errorMany server-side errors can lead to this error message. The event viewer log contains more detailed errors. In addition,you can disable the friendly HTTP error message to receive detailed error instructions. Other information about how to disable the HTTP friendly error message, check in the Microsoft knowledge base article: 294807 how to disable Internet Explorer 5 at the server end "show friendly HTTP error message" function500.12 - the application is busy restarting on the Web serverThis means that you are trying to load the ASP page while IIS restarts the application. Once the page is refreshed, this information disappears. Once the page is refreshed, the message appears again, possibly with anti-virus software scanning global.asa. For additional information, see the corresponding article in the Microsoft knowledge base: 248013 HTTP Error 500-12 Application Restarting (HTTP Error 500-12 applications are being restarted)The 500.13-web server is too busy500.15 - no direct request for Global. AsaThe 500.16-unc authorization credentials are incorrect (IIS6.0 proprietary)500.18-url authorization storage cannot be opened (IIS6.0 proprietary)500.100 - internal ASP errorThis error message will occur if you try to load the ASP page with error code. For more accurate error information, disablethe friendly HTTP error message. By default, this error message is only enabled on the default Web site. How about in the default Web site to see the error information of the other information please check phase should be in the Microsoft knowledge base article: 261200 shows the HTTP 500 error message and not the 500-500. The asp asp error information.The author thinks that there is a problem of directory permissions or no parent path.The 501-header value specifies the unimplemented configuration502 - the Web server received an invalid response (gateway error) as a gateway or proxy serverThis error message will occur if the CGI script that is trying to run does not return a valid HTTP header set.502.1 - CGI application timeout502.2-cgi application error503 - service unavailable (IIS6.0)504-gateway timeoutThe 505-http version is not supportedFTP code1 xx - certainly the preliminary answer: these status codeindicates an operation has been successful, but the client hope to continue to operate a new command before receive another answer.110 restart the tag replyThe service is ready to start after NNN minutes125 data connection is open and transmission is starting150 file status is normal, ready to open the data connectionFTP USES two ports: 21 to send commands and 20 to send data. The status code 150 indicates that the server is ready to open a new connection on port 20 and send some data.2xx - positive reply: an operation has been successfully completed. The client can execute the new command.200 command setNo command is executed. There are too many orders on the site211 system status, or system help reply212 directory213 file status214 help messageThe 215 NAME system type, in which NAME is the official system NAME listed in the Assigned Numbers document220 service ready,New user requests can be executed221 service closes the control connection. If appropriate, please log out225 data connection open, no transmission in progressClose the data connection. The requested file operation has been successful (for example, transferring files or dropping files)The command opens the data connection on port 20 to perform the operation, such as the transfer file. The operation completes successfully and the data connection is closed.227 enter the passive mode (h1, h2, h3, h4, p1, p2)230 users are logged in and continueAfter the client sends the correct password, the status code is displayed. It indicates that the user has logged in successfully.The requested file operation is correct and completedThe "PATHNAME" has been created.3xx - positive reply: the command has been successful, but the server needs more information from the client to complete the processing of the request.331 user name is correct, need passwordAfter the client sends the user name, the status code is displayed. The status code will be displayed regardless of whether the supplied user name is a valid account in the system.332 requires a login accountThe file operation of the 350 request is waiting for further information4xx - transient negative reply: this command is not successful, but the error is temporary. If the client retries the order, it may execute successfully.421 service unavailable, closing control connection425 cannot open data connection426 the Connection closed; Transfer abortedThe command opens the data connection to perform the operation, but the operation has been canceled and the data connection is closed.File operation of 450 unexecuted requests. File unavailable(for example, busy file)451 requested operation exception termination: local error is being processedThe operation of the request is not performed. The system storage space is not enough5xx - the complete answer to the negative: the order is not successful and the error is permanent. The same error will occur again if the client retries the command.500 syntax error, command is not recognized. This may include errors such as the command line too long501 has syntax errors in the parameters502 did not execute the command503 wrong sequence of commands504 no command to execute the parameter530 not logged inThe status code indicates that the user cannot log in because the user name and password combination are invalid. If you log in with a user account, you may enter the wrong user name or password, or you may choose to only allow anonymous access. If an anonymous account is used, the IIS configuration may reject anonymous access.532 storage files need accountsThe operation of 550 does not perform the request. File unavailable (for example, no file, no access)The command is not executed because the specified file is not available. For example, the file that you want to GET doesn't exist, or you try to PUT the file into a directory where you don't have access to it.The operation of the request is aborted: the unknown page typeFile operation exception termination for 552 requests: beyond the storage allocation (for the current directory or data set)The operation of 553 not performing the request. File names that are not allowed。

SIP协议错误代码大全

SIP协议错误代码大全

SIP协议错误代码大全1. 1xx系列 - 信息响应1. 100 Trying - 接收方正在处理请求,但没有给出最终响应。

2. 180 Ringing - 接收方正在振铃。

3. 183 Session Progress - 接收方已经在处理请求,并且期望发送一个最终响应。

2. 2xx系列 - 成功响应1.200OK-请求成功,客户端应该进行下一步操作。

2. 202 Accepted - 已经接受请求,但尚未完成处理。

3. 3xx系列 - 重定向响应1. 300 Multiple Choices - 请求的地址有多个选择,用户可以选择其中一个。

2. 301 Moved Permanently - 所请求的资源已经永久移动到新位置。

3. 302 Moved Temporarily - 所请求的资源已经临时移动到新位置。

4. 305 Use Proxy - 所请求的资源必须通过代理访问。

4. 4xx系列 - 客户端错误响应1. 400 Bad Request - 客户端请求有语法错误。

2. 401 Unauthorized - 需要用户身份验证。

3. 403 Forbidden - 服务器禁止访问所请求的资源。

4. 404 Not Found - 所请求的资源不存在。

5. 408 Request Timeout - 请求超时。

6. 415 Unsupported Media Type - 不支持的媒体类型。

5. 5xx系列 - 服务器错误响应1. 500 Server Internal Error - 服务器内部错误。

2. 501 Not Implemented - 服务器不支持实现请求的功能。

3. 502 Bad Gateway - 服务器作为网关或代理,从上游服务器接收到无效响应。

4. 503 Service Unavailable - 所请求的服务暂时不可用。

5. 504 Server Timeout - 服务器在等待上游服务器的响应时超时。

各类访问错误代码

各类访问错误代码

各类访问错误代码404 Not Found。

The 404 Not Found error is one of the most common HTTP status codes that users encounter when browsing the web. This error occurs when the server cannot find the requested resource, such as a web page or file. There are several reasons why this error may occur, including a mistyped URL, a broken link, or a deleted page. In this article, we will explore the causes of the 404 Not Found error and how to troubleshoot and fix it.Causes of the 404 Not Found Error。

There are several potential causes of the 404 Not Found error. Some of the most common include:1. Mistyped URL: One of the most common causes of the 404 error is a mistyped URL. If you accidentally type the wrong address into your browser, you will receive a 404 error because the server cannot find the requested resource.2. Broken Link: If a website contains a broken link that leads to a non-existent page, users will encounter a 404 error when they try to access that link.3. Deleted Page: If a web page has been deleted or moved to a different location, any links or bookmarks pointing to the old URL will result in a 404 error.4. Server Configuration Issues: Sometimes, the 404 error may be caused by server configuration issues, such as incorrect file permissions or a misconfigured .htaccess file.5. Website Maintenance: During website maintenance or updates, certain pages or files may be temporarily unavailable, resulting in a 404 error for users trying to access them.How to Fix the 404 Not Found Error。

sip错误代码

sip错误代码

sip错误代码1xx = 通知性应答100 正在尝试180 正在拨打181 正被转接182 正在排队183 通话进展2xx = 成功应答200 OK202 被接受:用于转介3xx = 转接应答300 多项选择301 被永久迁移302 被暂时迁移305 使用代理服务器380 替代服务4xx = 呼叫失败400 呼叫不当401 未经授权:只供注册机构使用,代理服务器应使用代理服务器授权407402 要求付费(预订为将来使用)403 被禁止的404 未发现:未发现用户405 不允许的方法406 不可接受407 需要代理服务器授权408 呼叫超时:在预定时间内无法找到用户410 已消失:用户曾经存在,但已从此处消失413 呼叫实体过大414 呼叫URI过长415 不支持的媒体类型416 不支持的URI方案420 不当扩展:使用了不当SIP协议扩展,服务器无法理解该扩展421 需要扩展423 时间间隔过短480 暂时不可使用481 通话/事务不存在482 检测到循环483 跳数过多484 地址不全485 模糊不清486 此处太忙487 呼叫被终止488 此处不可接受491 呼叫待批493 无法解读:无法解读 S/MIME文体部分5xx = 服务器失败500 服务器内部错误501 无法实施:SIP呼叫方法在此处无法实施502 不当网关503 服务不可使用504 服务器超时505 不支持该版本:服务器不支持SIP协议的这个版本513 消息过长6xx = 全局失败600 各处均忙603 拒绝604 无处存在606 不可使用代码详解:SIP协议应答码应答代码应答码是包含了,并且扩展了HTTP/1.1应答码。

并不是所有的HTTP/1.1应答码都适当应用,只有在折里指出的是适当的。

其他HTTP/1.1应答码不应当使用。

并且,SIP也定义了新的应答码系列,6xx。

1 临时应答1xx临时应答,也就是消息性质的应答,标志了对方服务器正在处理请求,并且还没有决定最后的应答。

网站经常出现的错误代码对照表

网站经常出现的错误代码对照表

这些状态代码表示临时的响应。

客户端在收到常规响应之前,应准备接收一个或多个1xx响应。

100-继续。

101-切换协议。

2xx-成功这类状态代码表明服务器成功地接受了客户端请求。

200-确定。

客户端请求已成功。

201-已创建。

202-已接受。

203-非权威性信息。

204-无内容。

205-重置内容。

206-部分内容。

3xx-重定向客户端浏览器必须采取更多操作来实现请求。

例如,浏览器可能不得不请求服务器上的不同的页面,或通过代理服务器重复该请求。

301-对象已永久移走,即永久重定向。

302-对象已临时移动。

304-未修改。

307-临时重定向。

4xx-客户端错误发生错误,客户端似乎有问题。

例如,客户端请求不存在的页面,客户端未提供有效的身份验证信息。

400-错误的请求。

401-访问被拒绝。

IIS定义了许多不同的401错误,它们指明更为具体的错误原因。

这些具体的错误代码在浏览器中显示,但不在IIS日志中显示:401.1-登录失败。

401.2-服务器配置导致登录失败。

401.3-由于ACL对资源的限制而未获得授权。

401.4-筛选器授权失败。

401.5-ISAPI/CGI应用程序授权失败。

401.7–访问被Web服务器上的URL授权策略拒绝。

这个错误代码为IIS6.0所专用。

403-禁止访问:IIS定义了许多不同的403错误,它们指明更为具体的错误原因:403.1-执行访问被禁止。

403.2-读访问被禁止。

403.3-写访问被禁止。

403.4-要求SSL。

403.5-要求SSL128。

403.6-IP地址被拒绝。

403.7-要求客户端证书。

403.8-站点访问被拒绝。

403.9-用户数过多。

403.10-配置无效。

403.11-密码更改。

403.12-拒绝访问映射表。

403.13-客户端证书被吊销。

403.14-拒绝目录列表。

403.15-超出客户端访问许可。

403.16-客户端证书不受信任或无效。

403.17-客户端证书已过期或尚未生效。

MQ错误代码一览

MQ错误代码一览

3091 => "Action value not valid.",4009 => "Allocation failed.",4005 => "Attribute value not valid.",4086 => "Batch interval not valid.",4087 => "Batch interval parameter not allowed for this channel type.",3037 => "Batch size not valid.",4024 => "Bind failed.",3049 => "Coded character-set identifier error.",4068 => "Cell directory is not available.",3007 => "Command identifier not valid.",3005 => "Control option not valid.",3002 => "Structure length not valid.",3004 => "Message sequence number not valid.",3006 => "Parameter count not valid.",3001 => "Type not valid.",3003 => "Structure version number is not valid.",3027 => "Count of parameter values not valid.",3026 => "Duplicate parameter.",3028 => "Structure length not valid.",3047 => "Parameter identifier is not valid.",3017 => "Duplicate parameter.",3009 => "Structure length not valid.",3014 => "Parameter identifier is not valid.",3068 => "Name count value not valid.",3066 => "Duplicate parameter.",3069 => "String length not valid.",3067 => "Total string length error.",3095 => "Conflicting parameters.",3018 => "Duplicate parameter.",3010 => "Structure length not valid.",3015 => "Parameter identifier is not valid.",3011 => "String length not valid.",4079 => "Channel automatic definition error.",4081 => "Channel automatic definition event error.",4082 => "Channel automatic definition event parameter not allowed for this channel type.",4083 => "Channel automatic definition exit name error.",4084 => "Channel automatic definition exit parameter not allowed for this channel type.",4080 => "Channel automatic definition parameter not allowed for this channel type.",4042 => "Channel already exists.",4038 => "Channel disabled.",4025 => "Channel in-doubt.",4031 => "Channel in use.",4044 => "Channel name error.",4064 => "Channel not active.",4032 => "Channel not found.",3062 => "Channel table value not valid.",3034 => "Channel type not valid.",3064 => "Channel instance type not valid.",3065 => "Channel status not found.",3088 => "ClusterName and ClusterNamelist attributes conflict.",3090 => "Cluster queue cannot be a transmission queue.",3008 => "Command failed.",4040 => "Commit failed.",3092 => "Library for requested communications protocol could not be loaded.",4011 => "Configuration error.",4017 => "Connection closed.",4012 => "Connection refused.",4062 => "Error in connection name parameter.",3052 => "Data conversion value not valid.",4043 => "Data too large.",3038 => "Disconnection interval not valid.",4054 => "Disconnection interval not allowed for this channel type.", 4067 => "Dynamic queue scope error.",3050 => "Encoding error.",4013 => "Invalid connection name.",3054 => "Escape type not valid.",3150 => "Content based filter expression not valid.",3012 => "Force value not valid.",4077 => "Heartbeat interval not valid.",4078 => "Heartbeat interval parameter not allowed for this channel type.",4010 => "Remote system not available.",3053 => "In-doubt value not valid.",4060 => "Keepalive interval not valid.",4003 => "New and existing objects have different type.",4020 => "Listener not started.",3041 => "Long retry count not valid.",4057 => "Long retry parameter not allowed for this channel type.", 3042 => "Long timer not valid.",4058 => "Long timer parameter not allowed for this channel type.", 3044 => "Maximum message length not valid.",4047 => "Message channel agent name error.",4053 => "Message channel agent name not allowed for this channel type.",3063 => "Message channel agent type not valid.",3023 => "Format not valid.",4061 => "Connection name parameter required but missing.",3029 => "Mode value not valid.",4026 => "MQCONN call failed.",4028 => "MQGET call failed.",4036 => "MQINQ call failed.",4027 => "MQOPEN call failed.",4029 => "MQPUT call failed.",4063 => "MQSET call failed.",4069 => "Message retry count not valid.",4070 => "Message-retry count parameter not allowed for this channel type.",4071 => "Channel message-retry exit name error.",4072 => "Message-retry exit parameter not allowed for this channel type.",4073 => "Message retry interval not valid.",4074 => "Message-retry interval parameter not allowed for this channel type.",4050 => "Channel message exit name error.",3016 => "Message length not valid.",3030 => "Message sequence number not valid.",3048 => "Message truncated.",3093 => "NetBIOS listener name not defined.",4088 => "Network priority value is not valid.",4089 => "Network priority parameter not allowed for this channel type.",4037 => "Queue is not a transmission queue.",4019 => "Communications manager not available.",4018 => "Not enough storage available.",4075 => "Nonpersistent message speed not valid.",4076 => "Nonpersistent message speed parameter not allowed for this channel type.",4001 => "Object already exists.",4008 => "Object name not valid.",4004 => "Object is open.",4002 => "Object has wrong type.",3020 => "Parameter count too big.",3019 => "Parameter count too small.",3035 => "Parameter sequence not valid.",3032 => "Ping Channel command failed.",3031 => "Data count not valid.",4030 => "Ping error.",3046 => "Purge value not valid.",3045 => "Put authority value not valid.",4059 => "Put authority parameter not allowed for this channel type.",3029 => "Quiesce value not valid.",3021 => "Queue already exists in cell.",3086 => "Queue manager coded character set identifier error.",3212 => "Queue manager not in Queue Sharing Group.",3022 => "Queue type not valid.",4007 => "Action not valid for the queue of specified type.",4051 => "Channel receive exit name error.",4015 => "Received data error.",4016 => "Receive failed.",4035 => "Remote queue manager terminating.",4034 => "Remote queue manager not available.",3025 => "Replace value not valid.",3089 => "RepositoryName and RepositoryNamelist attributes conflict.",4049 => "Channel security exit name error.",4048 => "Channel send exit name error.",4014 => "Send failed.",3043 => "Sequence wrap number not valid.",3039 => "Short retry count not valid.",4055 => "Short retry parameter not allowed for this channel type.", 3040 => "Short timer value not valid.",4056 => "Short timer parameter not allowed for this channel type.", 3013 => "Structure type not valid.",4085 => "Action suppressed by exit program.",4065 => "Channel terminated by security exit.",4006 => "Queue manager not known.",4033 => "Remote channel not known.",4039 => "User exit not available.",4041 => "Parameter not allowed for this channel type.",3151 => "Wrong user.",3036 => "Transmission protocol type not valid.",4045 => "Transmission queue name error.",4052 => "Transmission queue name not allowed for this channel type.",2129 => "Unable to load adapter connection module.",2133 => "Unable to load data conversion services modules.",2131 => "Adapter subsystem definition module not valid.",2132 => "Unable to load adapter subsystem definition module.",2138 => "Unable to load adapter disconnection module.",2204 => "Adapter not available.",2130 => "Unable to load adapter service module.",2127 => "Insufficient storage for adapter.",2001 => "Alias base queue not a valid type.",2002 => "Application already connected.",2103 => "Another queue manager already connected.",2183 => "Unable to load API crossing exit.",900 => "Lowest value for an application-defined reason codereturned by a data-conversion exit.",999 => "Highest value for application-defined reason code returned by a data-conversion exit.",2157 => "Primary and home ASIDs differ.",2003 => "Unit of work encountered fatal error or backed out.", 2303 => "Data could not be converted into a bag.",2326 => "Bag has wrong type for intended use.",2134 => "Begin-options structure not valid.",2125 => "Bridge started.",2126 => "Bridge stopped.",2004 => "Buffer parameter not valid.",2005 => "Buffer length parameter not valid.",2219 => "MQI call reentered before previous call complete.", 2277 => "Channel definition not valid.",2235 => "PCF header structure not valid.",2236 => "PCF integer list parameter structure not valid.",2237 => "PCF integer parameter structure not valid.",2238 => "PCF string list parameter structure not valid.",2239 => "PCF string parameter structure not valid.",2295 => "Channel activated.",2234 => "Automatic channel definition failed.",2233 => "Automatic channel definition succeeded.",2284 => "Channel conversion error.",2296 => "Channel cannot be activated.",2282 => "Channel started.",2283 => "Channel stopped.",2279 => "Channel stopped by user.",2007 => "Character attributes string not valid.",2008 => "Not enough space allowed for character attributes.", 2006 => "Length of character attributes not valid.",2187 => "Requested function not supported by CICS bridge.", 2140 => "Wait request rejected by CICS.",2278 => "Client connection fields not valid.",2266 => "Cluster workload exit failed.",2267 => "Unable to load cluster workload exit.",2268 => "Put calls inhibited for all queues in cluster.",2189 => "Cluster name resolution failed.",2322 => "Command server not available.",2139 => "Connect-options structure not valid.",2330 => "Coded character set identifier parameter not valid.", 2106 => "COD report option not valid for XCF queue.",2300 => "Command type not valid.",2368 => "Change Object",2367 => "Create Object",2369 => "Delete Object",2370 => "Refresh Object",2009 => "Connection to queue manager lost.",2273 => "Error processing MQCONN call.",2217 => "Not authorized for connection.",2202 => "Connection quiescing.",2203 => "Connection shutting down.",2160 => "Connection identifier already in use.",2097 => "Queue handle referred to does not save context.",2098 => "Context not available for queue handle referred to.", 2120 => "Converted data too big for buffer.",2190 => "Converted string too big for field.",2207 => "Correlation-identifier error.",2010 => "Data length parameter not valid.",2150 => "DBCS string not valid.",2198 => "Default transmission queue not local.",2199 => "Default transmission queue usage error.",2263 => "Destination environment data error.",2264 => "Destination name data error.",2135 => "Distribution header structure not valid.",2141 => "Dead letter header structure not valid.",2163 => "Recovery coordinator already exists.",2011 => "Name of dynamic queue not valid.",2308 => "Encoding not supported.",2012 => "Call not valid in environment.",2013 => "Expiry time not valid.",2014 => "Feedback code not valid.",2208 => "File-system error.",2110 => "Message format not valid.",2317 => "Format not supported.",2281 => "Function identifier not valid for service.",2016 => "Gets inhibited for the queue.",2186 => "Get-message options structure not valid.",2258 => "Group identifier not valid.",2017 => "No more handles available.",2320 => "Bag handle not valid.",2280 => "Configuration handle not valid.",2018 => "Connection handle not valid.",2142 => "MQ header structure not valid.",2019 => "Object handle not valid.",2148 => "IMS information header structure not valid.",2241 => "Message group not complete.",2242 => "Logical message not complete.",2259 => "Inconsistent browse specification.",2243 => "Message segments have differing CCSIDs.",2244 => "Message segments have differing encodings.",2313 => "Data type of item differs from previous occurrence of selector.",2185 => "Inconsistent persistence specification.",2245 => "Inconsistent unit-of-work specification.",2314 => "Index not valid.",2306 => "Index not present.",2020 => "Value for inhibit-get or inhibit-put queue attribute not valid.",2286 => "Initialization failed for an undefined reason.",2324 => "Command code is not a recognized inquiry command.", 2023 => "Integer attributes array not valid.",2021 => "Count of integer attributes not valid.",2022 => "Not enough space allowed for integer attributes.",2246 => "Message under cursor not valid for retrieval.",2316 => "ItemCount parameter not valid.",2327 => "ItemType parameter not valid.",2319 => "ItemValue parameter not valid.",2247 => "Match options not valid.",2025 => "Maximum number of connections reached.",2248 => "Message descriptor extension not valid.",2026 => "Message descriptor not valid.",2027 => "Missing reply-to queue.",2332 => "Message data does not begin with MQWIH.",2249 => "Message flags not valid.",2206 => "Message-identifier error.",2250 => "Message sequence number not valid.",2331 => "Use of message token not valid.",2218 => "Message length greater than maximum for channel.",2030 => "Message length greater than maximum for queue.",2031 => "Message length greater than maximum for queue manager.",2029 => "Message type in message descriptor not valid.",2301 => "Multiple instances of system data item not valid.",2136 => "Multiple reason codes returned.",2201 => "Name in use.",2194 => "Object name not valid for object type.",6117 => "Length is negative.",2325 => "Input bag contains one or more nested bags.",0 => "No reason to report.",2035 => "Not authorized for access.",2119 => "Application message data not converted.",2036 => "Queue not open for browse.",2037 => "Queue not open for input.",2038 => "Queue not open for inquire.",2039 => "Queue not open for output.",2093 => "Queue not open for pass all context.",2094 => "Queue not open for pass identity context.",2040 => "Queue not open for set.",2095 => "Queue not open for set all context.",2096 => "Queue not open for set identity context.",2270 => "No destination queues available.",2121 => "No participating resource managers registered.",2033 => "No message available.",2209 => "No message locked.",2034 => "Browse cursor not positioned on message.",2100 => "Object already exists.",2041 => "Object definition changed since opened.",2101 => "Object damaged.",2042 => "Object already open with conflicting options.",2152 => "Object name not valid.",2153 => "Object queue-manager name not valid.",2155 => "Object records not valid.",2043 => "Object type not valid.",2044 => "Object descriptor structure not valid.",2251 => "Message segment offset not valid.",2137 => "Object not opened successfully.",2046 => "Options not valid or not consistent.",2274 => "Option not valid in environment.",2045 => "Option not valid for object type.",2252 => "Original length not valid.",2123 => "Result of commit or back-out operation is mixed.",2124 => "Result of commit operation is pending.",2310 => "OutSelector parameter not valid.",2193 => "Error accessing page set data set.",2192 => "Page set data set full.",2321 => "Parameter missing.",2122 => "Participating resource manager not available.",2149 => "PCF structures not valid.",2047 => "Persistence not valid.",2048 => "Message on a temporary dynamic queue cannot be persistent.",2173 => "Put-message options structure not valid.",2158 => "Put message record flags not valid.",2050 => "Message priority not valid.",2049 => "Message Priority exceeds maximum value supported.", 2051 => "Put calls inhibited for the queue.",2159 => "Put message records not valid.",2290 => "Queue object already exists.",2052 => "Queue has been deleted.",2224 => "Queue depth high limit reached or exceeded.",2225 => "Queue depth low limit reached or exceeded.",2053 => "Queue already contains maximum number of messages.", 2222 => "Queue manager created.",2058 => "Queue manager name not valid or not known.",2223 => "Queue manager unavailable.",2059 => "Queue manager not available for connection.",2161 => "Queue manager quiescing.",2162 => "Queue manager shutting down.",2055 => "Queue contains one or more messages or uncommitted put or get requests.",2226 => "Queue service interval high.",2227 => "Queue service interval ok.",2056 => "No space available on disk for queue.",2057 => "Queue type not valid.",2154 => "Number of records present not valid.",2184 => "Remote queue name not valid.",2061 => "Report options in message descriptor not valid.",2102 => "Insufficient system resources available.",2156 => "Response records not valid.",2336 => "Command not valid.",2338 => "Duplicate parameter.",2334 => "MQRFH structure not valid.",2337 => "Parameter not valid.",2339 => "Parameter missing.",2335 => "<TT><VAR>NameValueString</VAR></TT> field not valid.",2220 => "Reference message header structure not valid.",2062 => "A message is already marked.",2063 => "Security error occurred.",2253 => "Length of data in message segment is zero.",2065 => "Count of selectors not valid.",2067 => "Attribute selector not valid.",2066 => "Count of selectors too big.",2068 => "Selector not applicable to queue type.",2309 => "Selector not present in bag.",2318 => "System selector not supported.",2305 => "Selector occurs more than once in bag.",2304 => "Selector not within valid range for call.",2299 => "Selector has wrong data type.",2312 => "Selector implies a data type not valid for call.",2289 => "Unexpected error occurred accessing service.",2285 => "Underlying service not available.",2099 => "Signal field not valid.",2069 => "Signal outstanding for this handle.",2070 => "No message returned (but signal request accepted).",2145 => "Source buffer parameter not valid.",2111 => "Source coded character set identifier not valid.",2113 => "Packed-decimal encoding in message not recognized.", 2114 => "Floating-point encoding in message not recognized.", 2112 => "Source integer encoding not recognized.",2143 => "Source length parameter not valid.",2261 => "Source environment data error.",2262 => "Source name data error.",2188 => "Call rejected by cluster-workload exit.",2105 => "Storage class error.",2071 => "Insufficient storage available.",2307 => "String parameter not valid.",2323 => "StringLength parameter not valid.",2311 => "String truncated (too long for output buffer).",2109 => "Call suppressed by exit program.",2024 => "No more messages can be handled within current unit of work.",2072 => "Syncpoint support not available.",2315 => "System bag is read-only and cannot be altered.",2328 => "System bag is read-only and cannot be deleted.",2302 => "System data item is read-only and cannot be altered.",2329 => "System data item is read-only and cannot be deleted.",2146 => "Target buffer parameter not valid.",2115 => "Target coded character set identifier not valid.",2117 => "Packed-decimal encoding specified by receiver not recognized.",2118 => "Floating-point encoding specified by receiver not recognized.",2116 => "Target integer encoding not recognized.",2144 => "Target length parameter not valid.",2287 => "Termination failed for an undefined reason.",2191 => "Character trigger message structure not valid.",2265 => "Trigger message structure not valid.",2075 => "Value for trigger-control attribute not valid.",2076 => "Value for trigger-depth attribute not valid.",2077 => "Value for trigger-message-priority attribute not valid.", 2078 => "Value for trigger-type attribute not valid.",2079 => "Truncated message returned (processing completed).",2080 => "Truncated message returned (processing not completed).", 2195 => "Unexpected error occurred.",2232 => "Unit of work not started.",2082 => "Unknown alias base queue.",2293 => "Authorization entity unknown to service.",2197 => "Unknown default transmission queue.",2292 => "Entity unknown to service.",2085 => "Unknown object name.",2086 => "Unknown object queue manager.",2288 => "Queue name not found.",2294 => "Reference object unknown.",2087 => "Unknown remote queue manager.",2104 => "Report option(s) in message descriptor not recognized.",2196 => "Unknown transmission queue.",2297 => "Unit of work canceled.",2128 => "Unit of work already started.",2255 => "Unit of work not available for the queue manager to use.", 2291 => "Unable to determine the user ID.",2090 => "Wait interval in MQGMO not valid.",2333 => "MQWIH structure not valid.",2256 => "Wrong version of MQGMO supplied.",2257 => "Wrong version of MQMD supplied.",2091 => "Transmission queue not local.",2092 => "Transmission queue with wrong usage.",2260 => "Transmission queue header structure not valid.",2107 => "MQXWAIT call canceled.",2108 => "Invocation of MQXWAIT call not valid.",。

IBM错误代码解释以及解决方法

IBM错误代码解释以及解决方法

IBM错误代码解释以及解决方法在使用IBM产品或服务的过程中,有时可能会遇到各种错误代码。

这些错误代码可能涉及到不同的问题,需要我们仔细检查和解决。

在本文中,我们将解释一些常见的IBM错误代码,并提供相应的解决方法。

1. 500 - Internal Server Error(内部服务器错误)这个错误代码表示服务器遇到了一个无法处理的问题。

可能的原因包括服务器配置错误、网络连接问题或应用程序错误。

解决方法包括:-检查服务器配置文件,确保配置正确。

-检查网络连接是否正常,尝试重启网络设备。

-使用日志文件来查找潜在的应用程序错误,并修复相应的代码。

2. 404 - Not Found(未找到)这个错误代码表示请求的资源在服务器上不存在。

可能的原因包括文件被误删除、链接错误或服务器配置问题。

解决方法包括:-检查请求的资源是否存在于服务器上。

如果不存在,可以尝试恢复文件或重新上传文件。

-检查链接是否正确。

如果链接错误,可以尝试修复链接或更改链接地址。

-检查服务器配置文件,确保资源的路径和文件名称正确。

3. 403 - Forbidden(禁止访问)这个错误代码表示服务器拒绝了对请求资源的访问。

可能的原因包括权限不足、IP地址被拦截或访问规则被禁止。

解决方法包括:-检查访问权限,确保用户有足够的权限来访问资源。

-检查IP地址是否被服务器拦截。

如果是,则可以尝试解除拦截或添加到允许访问列表。

-检查访问规则,确保没有禁止访问请求资源的规则。

4. 502 - Bad Gateway(网关错误)这个错误代码表示作为代理或网关的服务器从上游服务器接收到了一条无效的响应。

可能的原因包括上游服务器故障、网络连接问题或配置错误。

解决方法包括:-检查网络连接是否正常。

如果网络连接有问题,可以尝试重启网络设备或使用其他网络连接。

-检查代理或网关服务器的配置文件,确保配置正确。

5. 503 - Service Unavailable(服务不可用)这个错误代码表示服务器当前无法处理请求,可能是因为过载或维护。

Http请求返回状态码

Http请求返回状态码

Http请求返回状态码⼀、Http请求返回状态码1、2XX——成功请求返回信息为2开头的状态码时,所代表的意思是:状态码描述200 OK 请求成功201 Created 请求被创建完成,同时新的资源被创建202 Accepted 服务器已接受请求,但尚未处理203 No-Authoritative Information服务器已成功处理了请求,但返回的实体头部元信息不是在原始服务器上有效的确定集合,⽽是来⾃本地或者第三⽅的拷贝。

204 No Content 服务器成功处理了请求,但不需要返回任何实体内容,并且希望返回更新了的元信息。

响应可能通过实体头部的形式,返回新的或更新后的元信息。

205 Reset Content 服务器成功处理了请求,且没有返回任何内容。

206 Partial Content 服务器已经成功处理了部分 GET 请求。

207 Multi-Status 由WebDAV(RFC 2518)扩展的状态码,代表之后的消息体将是⼀个XML消息,并且可能依照之前⼦请求数量的不同,包含⼀系列独⽴的响应代码。

2、3XX——重定向请求返回信息为3开头的状态码时,所代表的意思是:状态码描述300 Multiple Choices 被请求的资源有⼀系列可供选择的回馈信息,每个都有⾃⼰特定的地址和浏览器驱动的商议信息。

301 Moved Permanently 被请求的资源已永久移动到新位置,并且将来任何对此资源的引⽤都应该使⽤本响应返回的若⼲个 URI 之⼀。

302 Move Temporarily 请求的资源临时从不同的 URI响应请求。

303 See Other 对应当前请求的响应可以在另⼀个 URL 上被找到,⽽且客户端应当采⽤ GET 的⽅式访问那个资源。

304 Not Modified 如果客户端发送了⼀个带条件的 GET 请求且该请求已被允许,⽽⽂档的内容(⾃上次访问以来或者根据请求的条件)并没有改变,则服务器应当返回这个状态码。

上传图片提示Server(IO)Error

上传图片提示Server(IO)Error

上传图片提示Server(IO)Error上传图片提示Server (IO) Error伺服器IO错误错误原因:.一般是php超时.对中文域名不支援.防火墙设定不当产生干扰~dedecms 上传图片出现ERROR:Copy Uploadfile Error!提示你确定你dedecms的上传资料夹的属性为777如果你做网站的应该知道怎么设定吧上传图片总是提示IO错误,怎么办1.如果你网站托管在虚拟空间,上传出现Server (IO) Error 错误,那么就找空间商吧;如果在30秒的时候就出现Server (IO) Error 错误,建议调整php.ini中的max_execution_time数值,步骤如下:开启php.ini→查询max_execution_time →max_execution_time = 600 ;每个PHP页面执行的最大时间值(秒),预设30秒→将预设30秒的数值调大注:未什么要设定那么大而不用预设的30. 那是你不能保证你上传的网速,如果网速太慢,时间太长,那多半会出现该问题!上传图片,总提示你上传图片的型别不符合。

一般上传图片要求gif、jpeg格式。

在天空软体站(sky.)下载个图片格式转换器就可以了。

满意请采纳提问时上传图片后,提示上传图片成功后,却没有图片显示啊?因为一般上传的图片都要稽核的~通过稽核的才会显示所以有一个时间差~耐心等等如果还是不能显示可以在右边找到投诉里面有未显示问题投诉选项一般都会比较迅速的处理问题的上传图片提示指令码错误那只能说遨游浏览器垃圾被或者你在浏览器上设定的不对,如:是否支援JAVA上传图片显示error #2038怎么办那是照片格式不对吾主题只能传GIF JPG和另外一种BMP的就不行。

你用【画图】把图片另存为JPG格式的再传就行了!照片大小一般没什么问题。

GODADDY 空间,网站后台无法上传图片,显示SERVER ERROR 有免费的网站设计说明和操作技巧。

windows7下安装IIS及遇到的问题解决办法

windows7下安装IIS及遇到的问题解决办法

win7安装IIS遇到的问题:问题1:HTTP 错误 404.2 - Not Found,由于 Web 服务器上的“ISAPI 和 CGI 限制”列表设置,无法提供您请求的页面。

点击IIS服务器根节点,找到右边“ISAPI和CGI限制”,把禁止项设置为允许,刷新问题2:WCF问题:“HTTP 错误 404.17 - Not Found 请求的内容似乎是脚本,因而将无法由静态文件处理程序来处理”解决方法Net3.5的WCF服务在IIS7中发布后,在IE中访问.svc文件出现以下错误:HTTP 错误 404.17 - Not Found请求的内容似乎是脚本,因而将无法由静态文件处理程序来处理。

后来发现在II7的WCF服务网站中<处理程序映射>中*.svc文件已经被.Net Framework4.0的处理程序aspnet_isapi.dll接管,看来是由于装了.Net Framework4.0 beta和 2010 beta2导致的,把原先的3.5给废了.不影响开发,但影响布署重新指定成.Net2.0中的处理程序aspnet_isapi.dll处理也不行.最后,干脆来个釜底抽薪吧,重新注册.Net 3.5的WCF结果,问题解决!<处理程序映射>中.svc也重新被.net 2.0接管最后:参考安装MSsql2005:下载:简体中文版(DVD)SQLServer2005SP3-KB955706-x86-CHS(SP3补丁,解决SQL2005在win7下运行不兼容的问题)微软这样解释:/archive/2009/05/14/sql-server-on-windows-7-rc-and-windows-server-2008-r2-rc.aspxsql server 2005 sp3下载地址/7/5/A/75A0B2DB-A41A-403C-83B6-DF26708C2836/SQLServer2005SP3-KB955706-x86-CHS.exe1、安装标准版SQL Server 2005 按照提示安装即可2、安装SQL Server 2005 SP3。

网络错误代码大全3篇

网络错误代码大全3篇

网络错误代码大全第一篇:常见网络错误代码及解决方法当我们访问网站、发送邮件或进行其他网络操作时,经常会遇到各种各样的错误代码。

以下是一些常见的网络错误代码及其解决方法:1. 404 Not Found:该错误代码表示客户端请求了一个不存在的资源。

解决方法:确认输入的URL是否正确,或者该资源是否已被删除。

2. 500 Internal Server Error:该错误代码表示服务器在处理请求时遇到了错误。

解决方法:刷新页面、清除浏览器缓存、联系网站管理员。

3. 503 Service Unavailable:该错误代码表示当前访问的网站停止服务,通常是由于网站升级、维护或过载引起的。

解决方法:稍后再试或联系网站管理员。

4. 400 Bad Request:该错误代码表示客户端发出的请求有错误,服务器无法识别。

解决方法:检查请求格式是否正确,或者联系网站管理员。

5. 401 Unauthorized:该错误代码表示没有权限访问该资源。

解决方法:检查输入的用户名和密码是否正确,或者联系网站管理员。

6. 403 Forbidden:该错误代码表示客户端请求被服务器拒绝,通常是由于用户权限不足引起的。

解决方法:联系网站管理员确认是否拥有足够的权限。

7. 408 Request Time-out:该错误代码表示请求超时,服务器未及时响应。

解决方法:稍后重试或联系网站管理员。

8. 504 Gateway Timeout:该错误代码表示网关超时,通常是由于服务器响应时间过长引起的。

解决方法:稍后再试或联系网站管理员。

以上是一些常见的网络错误代码及其解决方法,我们在使用网络时,经常要遇到这些问题。

如果遇到无法解决的问题,可以联系网站管理员或网络技术支持人员。

第二篇:网络错误代码中的常见网站错误及处理方法网络错误代码中的常见网站错误,是我们日常网站开发和维护中经常遇到的问题。

下面,我们就来了解一下这些常见网站错误及处理方法:1. 404 Not Found:该错误代码表示客户端请求了一个不存在的资源。

系列服务器报错代码

系列服务器报错代码

系列服务器报错代码引言服务器作为计算机网络中的关键设备,经常会遇到各种问题和错误。

本文将介绍一些常见的服务器报错代码,并提供相应的解决方案和建议。

1. 404 Not Found该错误代码表示服务器无法找到请求的资源。

可能的原因包括: - 资源不存在或被删除。

- URL输入错误或拼写错误。

- 服务器配置错误。

解决方案: - 检查URL是否正确。

可以尝试使用其他浏览器或设备重新访问。

- 确保请求的资源存在,并检查文件路径是否正确。

- 检查服务器配置文件(如Apache的配置文件)是否正确指向资源。

2. 500 Internal Server Error此错误代码表示服务器处理请求时发生内部错误。

一些可能的原因包括: - 服务器配置文件错误。

- 代码错误或漏洞。

- 资源耗尽或高负载导致服务器崩溃。

解决方案: - 检查服务器配置文件是否正确,特别是与服务器的连接和处理请求的相关设置。

- 检查代码中的错误和漏洞,并修复它们。

- 监测服务器的资源使用情况,例如内存、CPU等,并增加服务器的容量或优化代码。

3. 403 Forbidden该错误代码表示服务器拒绝提供请求的资源。

常见的原因有:- 权限设置错误,服务器不允许访问该资源。

- IP地址被拦截或被服务器屏蔽。

解决方案: - 检查服务器权限设置,确保所需资源对相应的用户或组是可访问的。

- 如果你是开发者,可以检查代码中是否有未经授权的访问尝试。

- 检查服务器的防火墙和屏蔽规则,确保请求的IP地址没有被拦截。

4. 502 Bad Gateway此错误代码表示服务器作为网关或代理服务器接收到无效的响应。

一些可能的原因包括: - 代理服务器配置错误。

- 后端服务器不可用或响应超时。

- 网络连接问题。

解决方案: - 检查代理服务器的配置,确保它正确指向后端服务器。

- 检查后端服务器的状态,如连接是否正常、响应是否超时等。

- 检查网络连接,确保代理服务器和后端服务器之间的网络正常工作。

网络安全错误错误代码

网络安全错误错误代码

网络安全错误错误代码网络安全错误错误代码如下:1. 401 Unauthorized: 该错误表示请求未经授权。

可能是由于缺少或错误的身份验证凭据导致的。

解决方法是提供正确的身份验证信息或者联系系统管理员获取授权。

2. 403 Forbidden: 该错误表示服务器拒绝了请求,且没有授权。

可能是由于访问了受限资源或者请求的身份验证凭据无效导致的。

解决方法是确保权限正确且有效,如果问题仍然存在,则需要联系系统管理员。

3. 404 Not Found: 该错误表示所请求的资源在服务器上未找到。

可能是由于URL地址错误、文件被删除或者文件名被修改导致的。

解决方法是检查URL地址是否正确,并确保文件存在且文件名无误。

4. 502 Bad Gateway: 该错误表示服务器作为网关或代理,从上游服务器接收到无效的响应。

可能是由于上游服务器故障或配置不正确导致的。

解决方法是检查上游服务器的状态,并确保能够正确响应。

5. 503 Service Unavailable: 该错误表示服务器暂时无法处理请求。

可能是由于服务器过载、维护或故障导致的。

解决方法是等待一段时间后重试,或者联系网络管理员检查服务器状态。

6. 504 Gateway Timeout: 该错误表示作为网关或代理的服务器在等待上游服务器的响应超时。

可能是由于上游服务器故障、网络连接问题或超时设置不正确导致的。

解决方法是检查上游服务器的可用性及网络连接,并确保设置合理的超时时间。

7. 1001 DNS Resolution Failed: 该错误表示DNS解析失败,即无法将域名解析为相应的IP地址。

可能是由于DNS配置错误、网络连接问题或者域名不存在导致的。

解决方法是检查DNS 配置,确保网络连接正常,并确认域名正确存在。

8. 1002 Connection Timed Out: 该错误表示连接超时,即无法在一定时间内建立服务器连接。

可能是由于网络连接问题、服务器故障或防火墙限制导致的。

rfc 2046定义的媒体类型的bnf构造 -回复

rfc 2046定义的媒体类型的bnf构造 -回复

rfc 2046定义的媒体类型的bnf构造-回复RFC 2046定义的媒体类型的BNF构造媒体类型(Media Type)是一个标准化的方法,用于描述Web上的不同资源的数据格式。

它由媒体类型(也称为MIME类型)和子类型组成,以及可选的参数。

RFC 2046定义了一种用于表示媒体类型的语法,即Backus-Naur Form(BNF),本文将详细介绍RFC 2046定义的媒体类型的BNF构造。

首先,我们需要了解一些基本的概念。

在RFC 2046中,媒体类型由三个部分组成,分别是主类型(top-level type)、子类型(subtype)和参数(parameters)。

主类型描述了媒体类型的大类别,如文本、图像、音频等;子类型描述了主类型下的具体细分,如文本类型下的纯文本、HTML、CSS等;参数是可选项,用于进一步细化媒体类型的特征,如字符集、编码方式等。

接下来,我们来看一下RFC 2046定义的媒体类型的BNF构造:media-type = type "/" subtype *( ";" parameter )type = discrete-type / composite-type / tokensubtype = tokenparameter = attribute "=" valueattribute = tokenvalue = token / quoted-string其中,type、subtype、parameter、attribute和value都是非终结符,用于描述媒体类型的不同部分。

/表示选择,*表示0个或多个,;表示分隔,=表示相等。

首先,我们来看type的构造。

type是主类型,它可以是离散类型(discrete-type)、复合类型(composite-type)或令牌(token)。

离散类型是具有单一值的主类型,如文本、图像、音频等;复合类型是具有多个值的主类型,通常用于描述混合型的媒体,如multipart类型;令牌用于表示非结构化的文本。

IISHTTP错误404.17-NotFound解决方法

IISHTTP错误404.17-NotFound解决方法

运行cmd,输入: 复制代码 代码如下: C:\Windows\\Framework\V4.0.30319\aspnet_regiis -i 注:C:\Windows\\Framework\V4.0.30319\ 是 netframework安装对应的路径; 如下图:
复制代码 代码如下:
%windir%\\Framework\v4.0.30319\aspn功后,重启一下iis, 理论上应可以解决导致404.17 not found 的大部分问题了; Win7中IIS出现“HTTP 错误 404.17 - Not Found 请求的内容似乎是脚本,因而将无法由静态文件处理程序来处理。 ”错误(已解决)
只需要重新安装一下就可以了。在Frameworv4.0的目录中安装的程序以管理员权限重新运行一下就可以了. 点开始-运行:
最近很多网站都开始使用2008r2来配置php运行环境因为2003微软已经开始不再支持就连现在的很多服务器都不支持2003了大家都提前进入win2008时代吧这篇文章为大家分析一下如何选择php版本
IISHTTP错误 404.17-NotFound解决方法
错误提示如下图:
出现这种情况的原因通常是因为先安装了Framework,后安装的IIS;

http错误代码及FTP错误代码含义大全详解

http错误代码及FTP错误代码含义大全详解

http错误代码及FTP错误代码含义大全详解http错误代码含义:"100" : Continue"101" : witching Protocols"200" : OK"201" : Created"202" : Accepted"203" : Non-Authoritative Information "204" : No Content"205" : Reset Content"206" : Partial Content"300" : Multiple Choices"301" : Moved Permanently"302" : Found"303" : See Other"304" : Not Modified"305" : Use Proxy"307" : Temporary Redirect"400" : Bad Request"401" : Unauthorized"402" : Payment Required"403" : Forbidden"404" : Not Found"405" : Method Not Allowed"406" : Not Acceptable"407" : Proxy Authentication Required "408" : Request Time-out"409" : Conflict"410" : Gone"411" : Length Required"412" : Precondition Failed"413" : Request Entity Too Large"414" : Request-URI Too Large"415" : Unsupported Media Type"416" : Requested range not satisfiable"417" : Expectation Failed"500" : Internal Server Error"501" : Not Implemented"502" : Bad Gateway"503" : Service Unavailable"504" : Gateway Time-out"505" : HTTP Version not supportedHTTP 400 - 请求无效HTTP 401.1 - 未授权:登录失败HTTP 401.2 - 未授权:服务器配置问题导致登录失败HTTP 401.3 - ACL 禁止访问资源HTTP 401.4 - 未授权:授权被筛选器拒绝HTTP 401.5 - 未授权:ISAPI 或 CGI 授权失败HTTP 403 - 禁止访问HTTP 403 - 对Internet 服务管理器(HTML) 的访问仅限于LocalhostHTTP 403.1 禁止访问:禁止可执行访问HTTP 403.2 - 禁止访问:禁止读访问HTTP 403.3 - 禁止访问:禁止写访问HTTP 403.4 - 禁止访问:要求 SSLHTTP 403.5 - 禁止访问:要求 SSL 128HTTP 403.6 - 禁止访问:IP 地址被拒绝HTTP 403.7 - 禁止访问:要求客户证书HTTP 403.8 - 禁止访问:禁止站点访问HTTP 403.9 - 禁止访问:连接的用户过多HTTP 403.10 - 禁止访问:配置无效HTTP 403.11 - 禁止访问:密码更改HTTP 403.12 - 禁止访问:映射器拒绝访问HTTP 403.13 - 禁止访问:客户证书已被吊销HTTP 403.15 - 禁止访问:客户访问许可过多HTTP 403.16 - 禁止访问:客户证书不可信或者无效HTTP 403.17 - 禁止访问:客户证书已经到期或者尚未生效HTTP 404.1 - 无法找到 Web 站点HTTP 404 - 无法找到文件HTTP 405 - 资源被禁止HTTP 406 - 无法接受HTTP 407 - 要求代理身份验证HTTP 410 - 永远不可用HTTP 412 - 先决条件失败HTTP 414 - 请求 - URI 太长HTTP 500 - 内部服务器错误HTTP 500.100 - 内部服务器错误 - ASP 错误HTTP 500-11 服务器关闭HTTP 500-12 应用程序重新启动HTTP 500-13 - 服务器太忙HTTP 500-14 - 应用程序无效HTTP 500-15 - 不允许请求 global.asaError 501 - 未实现HTTP 502 - 网关错误概要当用户试图通过HTTP 或文件传输协议(FTP) 访问一台正在运行Internet 信息服务 (IIS) 的服务器上的内容时,IIS 返回一个表示该请求的状态的数字代码。

HTTP协议错误代码大全

HTTP协议错误代码大全

HTTP协议错误代码⼤全HTTP1xx(临时响应):表⽰临时响应并需要请求者继续执⾏操作的状态代码。

100 (继续)请求者应当继续提出请求。

服务器返回此代码表⽰已收到请求的第⼀部分,正在等待其余部分。

101 (切换协议)请求者已要求服务器切换协议,服务器已确认并准备切换。

2xx (成功):表⽰成功处理了请求的状态代码。

注:200代表请求成,但是这并不意味着,返回的数据也是正确的200 (成功)服务器已成功处理了请求。

201 (已创建)请求成功并且服务器创建了新的资源。

202 (已接受)服务器已接受请求,但尚未处理。

203 (⾮授权信息)服务器已成功处理了请求,但返回的信息可能来⾃另⼀来源。

204 (⽆内容)服务器成功处理了请求,但没有返回任何内容。

205 (重置内容)服务器成功处理了请求,但没有返回任何内容。

206 (部分内容)服务器成功处理了部分 GET 请求。

3xx (重定向):接⼝重定向300 (多种选择)针对请求,服务器可执⾏多种操作。

服务器可根据请求者 (user agent) 选择⼀项操作,或提供操作列表供请求者选择。

301 (永久移动)请求的⽹页已永久移动到新位置。

服务器返回此响应(对 GET 或 HEAD 请求的响应)时,会⾃动将请求者转到新位置。

302 (临时移动)意味着接⼝将重定向到另⼀个URL中去303 (查看其他位置)请求者应当对不同的位置使⽤单独的 GET 请求来检索响应时,服务器返回此代码。

304 (未修改)⾃从上次请求后,请求的⽹页未修改过。

服务器返回此响应时,不会返回⽹页内容。

305 (使⽤代理)请求者只能使⽤代理访问请求的⽹页。

如果服务器返回此响应,还表⽰请求者应使⽤代理。

307 (临时重定向)服务器⽬前从不同位置的⽹页响应请求,但请求者应继续使⽤原有位置来进⾏以后的请求。

4xx(请求错误):这些状态代码表⽰请求可能出错,妨碍了服务器的处理。

400 (错误请求)Bad Request请求包含语法错误原因:(1)输⼊的参数多了或者少了(2)输⼊的参数错误(3)有时候服务器请求超时也会造成400错误401 (未授权)401 Unauthorized当前请求需要⽤户验证403 (禁⽌) Forbidden服务器已理解请求,但拒绝执⾏它原因:出现这类情况⼀般是访问这个接⼝需要⼀定的权限,但是访问者没有相应的访问权限解决⽅法:a.是否是登录的⽤户没有访问的权限;b.在服务端这个接⼝没有配置访问权限,即禁⽌任何⽤户访问404 (未找到)服务器找不到请求的⽹页。

短信错误代码对照表

短信错误代码对照表
16.2.1 CMPP 3.0 同步流程错误码 ............................................................................................................16-2 16.2.2 CMPP 2.0 同步流程错误码 ............................................................................................................16-3 16.3 CMPP 状态报告中 stat 字段的错误码....................................................................................................16-3 16.4 GNS 返回的应答错误码 ..........................................................................................................................16-5
15.2.1 消息处理成功.................................................................................................................................15-2 15.2.2 外部实体返回错误应答.................................................................................................................15-2 15.2.3 infoX-SMS GW 发送消息给外部实体失败...................................................................................15-2 15.2.4 infoX-SMS GW 对消息进行内部处理时产生的错误码...............................................................15-2 15.2.5 其他错误值说明.............................................................................................................................15-2 15.3 SMPP 话单错误码....................................................................................................................................15-3 15.3.1 SMPP 话单错误码分类 ..................................................................................................................15-3 15.3.2 infoX-SMS GW 的 AAAA 错误码 .................................................................................................15-4 15.3.3 SCP 返回的 BBBB 错误码 .............................................................................................................15-8 15.3.4 ISMG 返回的 CCCC 错误码 ........................................................................................................ 15-11 15.3.5 SP 返回的 DDDD 错误码............................................................................................................. 15-11 15.3.6 DSMP 返回的 EEEE 错误码 ........................................................................................................ 15-11 15.3.7 SMC 返回的 FFFF 错误码 ...........................................................................................................15-14 15.3.8 GGGG 错误码 ...............................................................................................................................15-17 15.3.9 XXXX 错误码 ...............................................................................................................................15-17
  1. 1、下载文档前请自行甄别文档内容的完整性,平台不提供额外的编辑、内容补充、找答案等附加服务。
  2. 2、"仅部分预览"的文档,不可在线预览部分如存在完整性等问题,可反馈申请退款(可完整预览的文档不适用该条件!)。
  3. 3、如文档侵犯您的权益,请联系客服反馈,我们会尽快为您处理(人工客服工作时间:9:00-18:30)。

Network Working Group S. Josefsson Request for Comments: 4027 April 2005 Category: InformationalDomain Name System Media TypesStatus of This MemoThis memo provides information for the Internet community. It doesnot specify an Internet standard of any kind. Distribution of thismemo is unlimited.Copyright NoticeCopyright (C) The Internet Society (2005).AbstractThis document registers the media types application/dns and text/dns in accordance with RFC 2048. The application/dns media type is used to identify data on the detached Domain Name System (DNS) formatdescribed in RFC 2540. The text/dns media type is used to identifymaster files as described in RFC 1035.Table of Contents1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 12. MIME Type Registration of application/dns . . . . . . . . . . 23. MIME Type Registration of text/dns . . . . . . . . . . . . . . 34. Security Considerations . . . . . . . . . . . . . . . . . . . 45. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 46. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 4A. Disclaimer and License . . . . . . . . . . . . . . . . . . . . 5 Normative References . . . . . . . . . . . . . . . . . . . . . 5 Informative References . . . . . . . . . . . . . . . . . . . . 5 Author’s Address . . . . . . . . . . . . . . . . . . . . . . . 5 Full Copyright Statements. . . . . . . . . . . . . . . . . . . 61. IntroductionDomain Name System (DNS) [1] information is traditionally stored intext files, so-called master files or zone files. The format isdescribed in section 5 of RFC 1035 [2].DNS data can also be stored in a "detached" format, intended forarchiving purposes, described in RFC 2540 [4].Josefsson Informational [Page 1]This document registers MIME media types for the two data formats,with the registration procedures described in RFC 2048 [3].2. MIME Type Registration of application/dnsTo: ietf-types@Subject: Registration of MIME media type application/dnsMIME media type name: applicationMIME subtype name: dnsRequired parameters: None.Optional parameters: None.Encoding considerations: The data format is binary, and data must be transfered unmodified. Using encodings intended for textual parts is not recommended.Security considerations: This media type identifies content as being detached DNS information, as documented in RFC 2540 [4]. This datamay be security relevant as per RFC 2538 [7] or may be securedinformation as per RFC 2535 [6]. Securing the content further may be done with standard techniques, such as OpenPGP [5] or CMS [9], butthis is outside of the scope here. Further security assessments are not available at this point.Interoperability considerations: The encoding of detached DNSinformation is, unlike textual master files, well defined. Nofurther interoperability considerations are known.Published specification: The format of data that could be tagged with this media type is documented in RFC 2540 [4].Applications that use this media type: DNS-related software,including software storing and using certificates stored in DNS.Additional information:Magic number(s): None.File extension(s): Unknown.Macintosh File Type Code(s): Unknown.Person & email address to contact for further information:Simon Josefsson simon@Intended usage: LIMITED USEJosefsson Informational [Page 2]Author/change controller: simon@3. MIME Type Registration of text/dnsTo: ietf-types@Subject: Registration of MIME media type text/dnsMIME media type name: textMIME subtype name: dnsRequired parameters: None.Optional parameters: None.Encoding considerations: The data is textual and should be transfered in a line-oriented mode. Text literals may contain CRLF within thetext. Binary transport is possible between systems that use the same end-of-line conventions. Master files are in general ASCII, butnon-ASCII octet values may occur and are treated as opaque values by DNS software (compare RFC 1035, section 5). The master file formatpermits encoding arbitrary octet values by using the "\DDD" encoding. The use of "\DDD" encoding can be more reliable than transportingnon-ASCII through MIME transports, if data passes through a gatewaythat re-encodes the character data.Security considerations: This media type identifies content as being DNS information in "master file" format, as documented in RFC 1035[2]. The DNS data may be security relevant as per to RFC 2538 [7],or may be secured information as per to RFC 2535 [6]. Securing thecontent further may be done with standard techniques, such as OpenPGP [5] or CMS [9], but this is outside of the scope here. Furthersecurity assessments are not available at this point.Interoperability considerations: There are interoperability concerns with master files, due to the widespread use of vendor-specificextensions. Non-ASCII comments within master files may have beenencoded in locally chosen character sets, which may be difficult totransport interoperably. Non-ASCII data in general can becomecorrupted by re-encoding gateways. To achieve interoperability, one can use the master file format described in the specification and the "\DDD" encoding for non-ASCII octets. Further interoperabilityissues with unrecognized RR types exist, which may be handled asdiscussed in section 5 of RFC 3597 [8].Published specification: The format of data that could be tagged with this MIME type is documented in RFC 1035 [2].Josefsson Informational [Page 3]Applications that use this media type: DNS-related software,including software storing and using certificates stored in DNS.Additional information:Magic number(s): None.File extension(s): ’soa’ and ’zone’ are known to be used.Macintosh file type code(s): Unknown.Person & email address to contact for further information:Simon Josefsson simon@Intended usage: LIMITED USEAuthor/change controller: simon@4. Security ConsiderationsSecurity considerations are discussed in the security considerations clauses of the MIME registrations in sections 2 and 3.5. IANA ConsiderationsThe IANA has registered the MIME media types application/dns andtext/dns by using the registration templates in sections 2 and 3, as per the procedure described in RFC 2048 [3].6. AcknowledgementsThanks to D. Eastlake for suggesting text/dns. Thanks to Keith Moore and Alfred Hoenes for reviewing this document. The authoracknowledges the RSA Laboratories for supporting the work that led to this document.Josefsson Informational [Page 4]A. Disclaimer and LicenseRegarding this entire document or any portion of it, the author makes no guarantees and is not responsible for any damage resulting fromits use. The author grants irrevocable permission to anyone to use, modify, and distribute it in any way that does not diminish therights of anyone else to use, modify, and distribute it, providedthat redistributed derivative works do not contain misleading author or version information. Derivative works need not be licensed under similar terms.Normative References[1] Mockapetris, P., "Domain names - concepts and facilities", STD13, RFC 1034, November 1987.[2] Mockapetris, P., "Domain names - implementation andspecification", STD 13, RFC 1035, November 1987.[3] Freed, N., Klensin, J., and J. Postel, "Multipurpose InternetMail Extensions (MIME) Part Four: Registration Procedures", BCP 13, RFC 2048, November 1996.[4] Eastlake 3rd, D., "Detached Domain Name System (DNS)Information", RFC 2540, March 1999.Informative References[5] Callas, J., Donnerhacke, L., Finney, H., and R. Thayer, "OpenPGP Message Format", RFC 2440, November 1998.[6] Eastlake 3rd, D., "Domain Name System Security Extensions", RFC 2535, March 1999.[7] Eastlake 3rd, D. and O. Gudmundsson, "Storing Certificates inthe Domain Name System (DNS)", RFC 2538, March 1999.[8] Gustafsson, A., "Handling of Unknown DNS Resource Record (RR)Types", RFC 3597, September 2003.[9] Housley, R., "Cryptographic Message Syntax (CMS)", RFC 3852,July 2004.Author’s AddressSimon JosefssonEMail: simon@Josefsson Informational [Page 5]Full Copyright StatementCopyright (C) The Internet Society (2005).This document is subject to the rights, licenses and restrictionscontained in BCP 78, and except as set forth therein, the authorsretain all their rights.This document and the information contained herein are provided on an "AS IS" basis and THE CONTRIBUTOR, THE ORGANIZATION HE/SHE REPRESENTS OR IS SPONSORED BY (IF ANY), THE INTERNET SOCIETY AND THE INTERNETENGINEERING TASK FORCE DISCLAIM ALL WARRANTIES, EXPRESS OR IMPLIED,INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THEINFORMATION HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIEDWARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Intellectual PropertyThe IETF takes no position regarding the validity or scope of anyIntellectual Property Rights or other rights that might be claimed to pertain to the implementation or use of the technology described inthis document or the extent to which any license under such rightsmight or might not be available; nor does it represent that it hasmade any independent effort to identify any such rights. Information on the procedures with respect to rights in RFC documents can befound in BCP 78 and BCP 79.Copies of IPR disclosures made to the IETF Secretariat and anyassurances of licenses to be made available, or the result of anattempt made to obtain a general license or permission for the use of such proprietary rights by implementers or users of thisspecification can be obtained from the IETF on-line IPR repository at /ipr.The IETF invites any interested party to bring to its attention anycopyrights, patents or patent applications, or other proprietaryrights that may cover technology that may be required to implementthis standard. Please address the information to the IETF at ietf-ipr@.AcknowledgementFunding for the RFC Editor function is currently provided by theInternet Society.Josefsson Informational [Page 6]。

相关文档
最新文档