├── Makefile ├── README.md ├── httpstatus.7 ├── httpstatus.7.pdf └── httpstatus.7.txt /Makefile: -------------------------------------------------------------------------------- 1 | NAME=httpstatus 2 | PREFIX?=/usr/local 3 | 4 | all: help 5 | 6 | help: 7 | @echo "The following targets are available:" 8 | @echo "install install just the 'httpstatus.7' manual page into ${PREFIX}" 9 | @echo "install-all install the 'httpstatus.7' manual page into ${PREFIX}," 10 | @echo " then symlink each http status code so that you can run" 11 | @echo " e.g., 'man http:404'." 12 | @echo "txt generate a text version of the manual page" 13 | @echo "pdf generate a PDF version of the manual page" 14 | 15 | install: 16 | mkdir -p ${PREFIX}/share/man/man7/ 17 | install -c -m 444 ${NAME}.7 ${PREFIX}/share/man/man7/${NAME}.7 18 | 19 | install-all: install 20 | for c in $$(awk '/^.It [0-9][0-9]/ { print $$2 }' httpstatus.7); do \ 21 | ln -s ${NAME}.7 ${PREFIX}/share/man/man7/http:$$c.7; \ 22 | done 23 | 24 | txt: ${NAME}.7.txt 25 | 26 | ${NAME}.7.txt: ${NAME}.7 27 | groff -Tascii -mandoc $? | col -b >$@ 28 | 29 | pdf: ${NAME}.7.pdf 30 | 31 | ${NAME}.7.pdf: ${NAME}.7.ps 32 | ps2pdf $? 33 | rm $? 34 | 35 | ${NAME}.7.ps: ${NAME}.7 36 | groff -man -Tps $? > $@ 37 | 38 | clean: 39 | rm -f ${NAME}.7.txt ${NAME}.7.pdf 40 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | HTTP Status Codes 2 | ================= 3 | 4 | Sure, you know your `200 Ok`, `404 Not Found`, and 5 | `500 Internal Server Error` HTTP status codes, but 6 | beyond those, chances are you need to look up their 7 | specific meaning. Pulling up a website for those is 8 | fine, but wouldn't it make more sense to just type 9 | `man httpstatus` and see all the status codes? 10 | 11 | I know, I thought so, too. So here's a manual page 12 | that provides a terse summary of the standardized HTTP 13 | status codes as derived from the various RFCs. 14 | 15 | If you're too lazy even to install the manual page, 16 | [here's a 17 | PDF](https://raw.githubusercontent.com/jschauma/httpstatus/main/httpstatus.7.pdf) 18 | and a [plain 19 | text](https://raw.githubusercontent.com/jschauma/httpstatus/main/httpstatus.7.txt) 20 | version. 21 | 22 | ## Installation 23 | 24 | You can install the manual page by running `make 25 | install`. This will copy the manual page into the 26 | subdirectory `share/man/man7` under `PREFIX`. 27 | 28 | The Makefile defaults to `/usr/local` as the prefix, 29 | but you can change that, if you like: 30 | 31 | ``` 32 | $ make PREFIX=~ install 33 | ``` 34 | 35 | If you'd like to be able to call up the manual page 36 | for each HTTP status code using e.g., `man http:451`, 37 | then you can run 38 | 39 | ``` 40 | $ make install-all 41 | ``` 42 | 43 | This will create symlinks for each status code to 44 | `httpstatus(7)`. 45 | 46 | 47 | See also 48 | ======== 49 | 50 | Standardized HTTP status codes: 51 | 52 | * [Wikipedia List of HTTP status codes](https://en.wikipedia.org/wiki/List_of_HTTP_status_codes) 53 | * [IANA list of HTTP status codes](https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml) 54 | * [Mozilla Developer Network: HTTP response status codes](https://developer.mozilla.org/en-US/docs/Web/HTTP/Status) 55 | 56 | Unofficial HTTP status codes: 57 | 58 | * [Akamai Enterprise Application Access Status Codes](https://techdocs.akamai.com/eaa/docs/app-response-codes-login-events-err) 59 | * [Edgio Status Codes](https://docs.edg.io/guides/v4/status_codes) 60 | * [Shopify API response status and error codes](https://shopify.dev/docs/api/usage/response-codes) 61 | -------------------------------------------------------------------------------- /httpstatus.7: -------------------------------------------------------------------------------- 1 | .\" Most of the text in this manual page is either 2 | .\" copied verbatim or derived from the various RFCs 3 | .\" or the Wikipedia article listed in the SEE ALSO 4 | .\" section. That article itself is largely copied 5 | .\" verbatim or derived from the various RFCs, and 6 | .\" licensed under the Creative Commons 7 | .\" Attribution-Share-Alike License 3.0 8 | .\" (https://creativecommons.org/licenses/by-sa/3.0/). 9 | .\" 10 | .\" As far as the markup here is concerned, please 11 | .\" feel free to take this file an do with it what you 12 | .\" please, so long as your lawyers agree that this is 13 | .\" allowed by the original sources' licensing terms. 14 | .\" I am not a lawyer, and know better to play one on 15 | .\" the internet. 16 | .\" 17 | .\" Jan Schaumann , July 2021 18 | .Dd December 14, 2023 19 | .Dt httpstatus 7 20 | .Os 21 | .Sh NAME 22 | .Nm httpstatus 23 | .Nd HTTP status codes 24 | .Sh DESCRIPTION 25 | This manual page documents the HTTP status codes 26 | commonly issued by a web server in response to a 27 | client request. 28 | The status codes in this manual page are based on the 29 | information found in RFC7231 unless otherwise noted. 30 | .Pp 31 | HTTP status codes fall into one of five classes, 32 | identified by the first digit as follows: 33 | .Bl -tag -width XX 34 | .It 1xx (Informational) 35 | The request was received, continuing process. 36 | .It 2xx (Successful) 37 | The request was successfully received, understood, and accepted. 38 | .It 3xx (Redirection) 39 | Further action needs to be taken in order to complete 40 | the request. 41 | .It 4xx (Client Error) 42 | The request contains bad syntax or cannot be 43 | fulfilled. 44 | .It 5xx (Server Error) 45 | The server failed to fulfill an apparently valid 46 | request. 47 | .El 48 | .Sh 1xx STATUS CODES 49 | .Bl -tag -width XX 50 | .It 100 Continue 51 | The server has received the initial part of the 52 | request and the client should proceed to send the 53 | remainder. 54 | .It 101 Switching Protocols 55 | The server agrees to the client's request to switch 56 | protocols via the RFC7230 "Upgrade" header. 57 | .It 102 Processing 58 | The server has has accepted the complete request, 59 | but has not yet completed it. 60 | (WebDAV; RFC2518) 61 | .It 103 Early Hints 62 | The server is likely to send a final response with the 63 | header fields included in the informational response. 64 | (RFC8297) 65 | .El 66 | .Sh 2xx STATUS CODES 67 | .Bl -tag -width XX 68 | .It 200 Ok 69 | The request has succeeded. 70 | .It 201 Created 71 | The request has been fulfilled and has resulted in one 72 | or more new resources being created. 73 | .It 202 Accepted 74 | The request has been accepted for processing, but the 75 | processing has not been completed. 76 | .It 203 Non-Authoritative Information 77 | The request was successful but the enclosed payload has 78 | been modified from that of the origin server's 200 79 | (OK) response by a transforming proxy. 80 | .It 204 \&No Content 81 | The server has successfully fulfilled the request; 82 | there is no additional content to send in the response 83 | payload body. 84 | .It 205 Reset Content 85 | The server has fulfilled the request; the client 86 | should reset its document view. 87 | .It 206 Partial Content 88 | The server is successfully fulfilling a range request 89 | for the target resource based on the client's "Range" 90 | header. (RFC7233) 91 | .It 207 Multi-Status 92 | Multiple resources were to be affected by the COPY, 93 | but errors on some of them prevented the operation 94 | from taking place. (WebDAV; RFC4918) 95 | .It 208 Already Reported 96 | Indicates that members of multiple bindings from a previous 97 | multi-status response are not repeated. 98 | (WebDAV; RFC5842) 99 | .It 226 IM Used 100 | The server has fulfilled a GET request for the 101 | resource, and the response is a representation of the 102 | result of one or more instance- manipulations applied 103 | to the current instance. 104 | (RFC3229) 105 | .El 106 | .Sh 3xx STATUS CODES 107 | .Bl -tag -width XX 108 | .It 300 Multiple Choices 109 | The target resource has more than one representation 110 | which the client may choose from via Content 111 | Negotiation. 112 | .It 301 Moved Permanently 113 | The target resource has been assigned a new permanent 114 | URI and any future references to this resource ought 115 | to use one of the enclosed URIs. 116 | .It 302 Found 117 | The target resource resides temporarily under a 118 | different URI. 119 | .It 303 See Other 120 | The server is redirecting the user agent to a 121 | different resource, as indicated by a URI in the 122 | Location header field. 123 | .It 304 Not Modified 124 | A conditional GET or HEAD request has been received 125 | and would have resulted in a 200 (OK) response if it 126 | were not for the fact that the condition evaluated to 127 | false. 128 | (RFC7232) 129 | .It 305 Use Proxy 130 | The requested resource MUST be accessed through the 131 | proxy given by the Location field. (RFC2616) 132 | Deprecated due to security concerns regarding in-band 133 | configuration of a proxy. 134 | .It 306 Switch Proxy 135 | No longer used. 136 | Originally generated by a proxy server to indicate 137 | that the client or proxy should use the information in 138 | the accompanying 'Set- proxy' header to choose a proxy 139 | for subsequent requests. 140 | .It 307 Temporary Redirect 141 | The target resource resides temporarily under a 142 | different URI and the user agent MUST NOT change the 143 | request method if it performs an automatic redirection 144 | to that URI. 145 | .It 308 Permanent Redirect 146 | The target resource has been assigned a new permanent 147 | URI and any future references to this resource ought 148 | to use one of the enclosed URIs. 149 | (RFC7538) 150 | .El 151 | .Sh 4xx STATUS CODES 152 | .Bl -tag -width XX 153 | .It 400 Bad Request 154 | The server cannot or will not process the request due 155 | to something that is perceived to be a client error 156 | (e.g., malformed request syntax, invalid request 157 | message framing, or deceptive request routing). 158 | .It 401 Unauthorized 159 | The request has not been applied because it lacks 160 | valid authentication credentials for the target 161 | resource. 162 | .It 402 Payment Required 163 | Reserved for future use. 164 | .It 403 Forbidden 165 | The server understood the request but refuses to 166 | authorize it. 167 | .It 404 Not Found 168 | The origin server did not find a current 169 | representation for the target resource or is not 170 | willing to disclose that one exists. 171 | .It 405 Method Not Allowed 172 | The method received in the request-line is known by 173 | the origin server but not supported by the target 174 | resource. 175 | .It 406 Not Acceptable 176 | The target resource does not have a current 177 | representation that would be acceptable to the user 178 | agent, such as due to the client's "Accept" header. 179 | .It 407 Proxy Authentication Required 180 | The client needs to authenticate itself in order to 181 | use a proxy. 182 | (RFC7235) 183 | .It 408 Request Timeout 184 | The server did not receive a complete request message 185 | within the time that it was prepared to wait. 186 | .It 409 Conflict 187 | The request could not be completed due to a conflict 188 | with the current state of the target resource. 189 | .It 410 Gone 190 | Access to the target resource is no longer available 191 | at the origin server; this condition is likely to be 192 | permanent. 193 | .It 411 Length Required 194 | The server refuses to accept the request without a 195 | defined Content-Length. 196 | .It 412 Precondition Failed 197 | One or more conditions given in the request header 198 | fields evaluated to false when tested on the server. 199 | (RFC7232) 200 | .It 413 Payload Too Large 201 | The server is refusing to process a request because 202 | the request payload is larger than the server is 203 | willing or able to process. 204 | .It 414 URI Too Long 205 | The server is refusing to service the request because 206 | the request-target is longer than the server is 207 | willing to interpret. 208 | .It 415 Unsupported Media Type 209 | The origin server is refusing to service the request 210 | because the payload is in a format not supported by 211 | this method on the target resource. 212 | .It 416 Range Not Satisfiable 213 | None of the ranges in the request's Range header field 214 | overlap the current extent of the selected resource or 215 | the set of ranges requested has been rejected due to 216 | invalid ranges or an excessive request of small or 217 | overlapping ranges. 218 | (RFC7233) 219 | .It 417 Expectation Failed 220 | The expectation given in the request's Expect header 221 | field could not be met by at least one of the inbound 222 | servers. 223 | .It 418 I'm a teapot 224 | An attempt to brew coffee was made, even though the 225 | target is a teapot. 226 | (RFC2324) 227 | .It 421 Misdirected Request 228 | The request was directed at a server that is not able 229 | to produce a response. 230 | (RFC7540) 231 | .It 422 Unprocessable Entity 232 | The server understands the content type of the request 233 | entity and the syntax of the request entity is 234 | correct, but was unable to process the contained 235 | instructions. 236 | (WebDAV; RFC4918) 237 | .It 423 Locked 238 | The source or destination resource of a method is 239 | locked. 240 | (WebDAV; RFC4918) 241 | .It 424 Failed Dependency 242 | The method could not be performed on the resource 243 | because the requested action depended on another 244 | action and that action failed. 245 | (WebDAV; RFC4918) 246 | .It 425 Too Early 247 | The server is unwilling to risk processing a request 248 | that might be replayed. 249 | (RFC8470) 250 | .It 426 Upgrade Required 251 | The server refuses to perform the request using the 252 | current protocol but might be willing to do so after 253 | the client upgrades to a different protocol. 254 | .It 428 Precondition Required 255 | The origin server requires the request to be 256 | conditional. 257 | (RFC6585) 258 | .It 429 Too Many Requests 259 | The user has sent too many requests in a given amount 260 | of time. 261 | (RFC6585) 262 | .It 431 Request Header Fields Too Large 263 | The server is unwilling to process the request because 264 | its header fields are too large. 265 | (RFC6585) 266 | .It 451 Unavailable For Legal Reasons 267 | The server is denying access to the resource as a 268 | consequence of a legal demand. 269 | (RFC7725) 270 | Named after Ray Bradbury's "Fahrenheit 451". 271 | .El 272 | .Sh 5xx STATUS CODES 273 | .Bl -tag -width XX 274 | .It 500 Internal Server Error 275 | The server encountered an unexpected condition that 276 | prevented it from fulfilling the request. 277 | .It 501 Not Implemented 278 | The server does not support the functionality required 279 | to fulfill the request. 280 | .It 502 Bad Gateway 281 | The server, while acting as a gateway or proxy, 282 | received an invalid response from an inbound server it 283 | accessed while attempting to fulfill the request. 284 | .It 503 Service Unavailable 285 | The server is currently unable to handle the request 286 | due to a temporary overload or scheduled maintenance, 287 | which will likely be alleviated after some delay. 288 | .It 504 Gateway Timeout 289 | The server, while acting as a gateway or proxy, did 290 | not receive a timely response from an upstream server 291 | it needed to access in order to complete the request. 292 | .It 505 HTTP Version Not Supported 293 | The server does not support, or refuses to support, 294 | the major version of HTTP that was used in the request 295 | message. 296 | .It 506 Variant Also Negotiates 297 | The server's chosen variant resource is configured to 298 | engage in transparent content negotiation itself, and 299 | is therefore not a proper end point in the negotiation 300 | process. 301 | (RFC2295) 302 | .It 507 Insufficient Storage 303 | The method could not be performed on the resource 304 | because the server is unable to store the 305 | representation needed to successfully complete the 306 | request. 307 | (WebDAV; RFC4918) 308 | .It 508 Loop Detected 309 | The server terminated an operation because it 310 | encountered an infinite loop while processing a 311 | request with "Depth: infinity". 312 | (WebDAV; RFC5842) 313 | .It 510 Not Extended 314 | The policy for accessing the resource has not been met 315 | in the request. 316 | (RFC2774) 317 | .It 511 Network Authentication Required 318 | The client needs to authenticate to gain network 319 | access. 320 | (RFC6585) 321 | .El 322 | .Sh NON STANDARD HTTP STATUS CODES 323 | In addition to the above, several HTTP server or proxy 324 | implementations include custom status codes, 325 | particularly in the 4xx and 5xx classes. 326 | .Bl -tag -width XX 327 | .It 000 (AWS ELB) 328 | Used by AWS Elastic Load Balancing with HTTP/2 GOAWAY 329 | frame if the compressed length of any of the headers 330 | exceeds 8K bytes or if more than 10K requests are 331 | served through one connection exceeds 10,000. 332 | .It 000 (curl) 333 | Used by 334 | .Xr curl 1 335 | to indicate a failed execution. 336 | .It 000 Client-Side Abort (Akamai LDS) 337 | Used by Akamai Log Delivery Services if a download was 338 | terminated by the end-user before the edge server is 339 | able to send back the response header. 340 | .It 000 (Looker Studio) 341 | No HTTP code was received. 342 | .It 218 This is fine (Apache httpd) 343 | A catch-all error condition displayed instead of a 4xx 344 | or 5xx error, allowing the passage of message bodies 345 | through the server when the 346 | .Ar ProxyErrorOverride 347 | setting is enabled. 348 | .It 299 Deprecated (Linode) 349 | The request was successful, but involved a deprecated 350 | endpoint. 351 | .It 419 Page Expired (Laravel) 352 | A CSRF Token is missing, expired, or cannot be verified. 353 | .It 430 Shopify Security Rejection (Shopify) 354 | The request was deemed malicious. 355 | .It 440 Login Time-out (Microsoft IIS) 356 | The client's session has expired and must log in again. 357 | .It 444 \&No Response (nginx) 358 | Used by the ngx_http_rewrite_module to instruct 359 | the server to close the connection without sending a 360 | response header. 361 | .It 449 Retry With Status Code (Microsoft IIS) 362 | The request cannot be satisfied because insufficient 363 | information was provided by the client. 364 | .It 450 Blocked by Windows Parental Controls (Microsoft) 365 | Windows Parental Controls are turned on and are 366 | blocking access to the requested webpage. 367 | .It 451 Redirect (Microsoft Exchange) 368 | Used by Microsoft Exchange ActiveSync to indicate that 369 | the client is attempting to connect to the wrong 370 | server, or if there is a more efficient server to use 371 | to reach the user's mailbox 372 | .It 460 (AWS ELB) 373 | The client closed the connection with the load balancer 374 | before the idle timeout period elapsed. 375 | .It 462 Not Allowed (Fastly) 376 | The client's IP was blocked. 377 | .It 463 (AWS ELB) 378 | The load balancer received an X-Forwarded-For request 379 | header with too many IP addresses. 380 | .It 464 (AWS ELB) 381 | Incompatible protocol versions between the client and 382 | the origin server. 383 | .It 492 User Access Forbidden (Akamai EAA) 384 | The client is not authorized to access the application. 385 | .It 493 Unsupported Browser (Akamai EAA) 386 | The client did not send a Server Name Identification 387 | (SNI) in the TLS handshake. 388 | .It 494 Request Header Too Large (nginx) 389 | The client sent too large a request or too long a 390 | header line. 391 | .It 494 Request Header Or Cookie Too Large (Akamai EAA) 392 | An HTTP Request Header is bigger than the configured 393 | buffer value. 394 | .It 498 Invalid Token (Esri) 395 | Used by the Esri ArcGIS Server to indicate an expired 396 | or otherwise invalid token. 397 | .It 495 SSL Certificate Error (nginx) 398 | The client has provided an invalid client certificate. 399 | .It 496 496 SSL Certificate Required (nginx) 400 | A client certificate is required but was not provided. 401 | .It 497 HTTP Request Sent to HTTPS Port (nginx) 402 | The client has made an HTTP request to an HTTPS port. 403 | .It 499 Client Closed Request (nginx) 404 | The client has closed the request before the server 405 | could send a response. 406 | .It 499 Token Required (Esri) 407 | Used by the Esri ArcGIS Server to indicate that a 408 | token is required but was not submitted. 409 | .It 503 Loop Detected (Fastly) 410 | A request appears to originate from the same Fastly 411 | service that it is trying to invoke, or the request 412 | has transited too many Fastly servers. 413 | .It 509 Bandwidth Limit Exceeded (Apache httpd / cPanel) 414 | The server has exceeded the bandwidth specified 415 | by the server administrator. 416 | .It 520 Web Server Returned an Unknown Error (Cloudflare) 417 | The origin server returned an empty, unknown, or 418 | unexpected response to Cloudflare. 419 | .It 521 Web Server Is Down (Cloudflare) 420 | The origin server refused connections. 421 | .It 522 Connection Timed Out (Cloudflare) 422 | Time out when contacting the origin server. 423 | .It 523 Origin Is Unreachable (Cloudflare) 424 | The origin server was unreachable. 425 | .It 524 A Timeout Occurred (Cloudflare) 426 | After a successful TCP connection to the origin server 427 | the HTTP response timed out. 428 | .It 525 SSL Handshake Failed (Cloudflare) 429 | TLS handshake failure with the origin server. 430 | .It 526 Invalid SSL Certificate (Cloudflare / Cloud Foundry) 431 | Unable to validate the origin server's TLS certificate. 432 | .It 527 Railgun Error (Cloudflare) 433 | Connection interrupted between Cloudflare and the 434 | origin server's Railgun server. 435 | .It 529 Site is overloaded (Qualys SSLabs) 436 | API service is overloaded. 437 | .It 530 Internal Edgio Error (Edgio) 438 | An unexpected error. 439 | .It 530 (Cloudflare) 440 | Used by Cloudflare as a generic error status code. 441 | More details can be found in the accompanying HTML 442 | body describing a 1XXX error code. 443 | .It 530 Site is frozen (Pantheon) 444 | A site that has been frozen due to inactivity. 445 | .It 530 Origin DNS Error (Shopify) 446 | Cloudflare can't resolve the requested DNS record. 447 | .It 531 Project Upstream Connection Error (Edgio) 448 | Unable to establish a connection to the origin server. 449 | .It 532 Project Response Too Large (Edgio) 450 | A returned a response size was greater than the allowed maximum. 451 | .It 533 Project Upstream TLS Error (Edgio) 452 | Unable to establish a TLS connection to the origin. 453 | .It 534 Project Error (Edgio) 454 | The project's serverless code has failed unexpectedly 455 | or has issued a malformed response. 456 | .It 535 Unknown Project (Edgio) 457 | Missing or mismatching Host header. 458 | .It 536 Project HTTP Response Timeout (Edgio) 459 | Time out when contacting the origin server. 460 | .It 537 Project DNS Resolution Error (Edgio) 461 | The proxy was unable to resolve the host name. 462 | .It 538 Project Request Loop (Edgio) 463 | The request went through too many Edgio servers. 464 | .It 539 Project Timeout (Edgio) 465 | The project's serverless code did not respond in time. 466 | .It 540 Temporarily Disabled (Shopify) 467 | The requested endpoint has been temporarily disabled. 468 | .It 540 Connectivity Disrupted (Akamai EAA) 469 | The connector does not have dial-out connections to 470 | either the data POP for the application or access to 471 | the directory. 472 | .It 540 Out of Memory (Edgio) 473 | The project's serverless code caused an out-of-memory 474 | situation. 475 | .It 541 Edgio Out of Workers (Edgio) 476 | Traffic was too high to be scheduled for processing 477 | within the scheduling timeout. 478 | .It 542 Internal Database Error (Akamai EAA) 479 | The data POP cannot reach the authentication database. 480 | .It 542 Project Header Overflow (Edgio) 481 | The project's request or response had too many HTTP 482 | headers. 483 | .It 543 IdP Communication Error (Akamai EAA) 484 | The data POP cannot reach the IdP or directory service. 485 | .It 543 Global Upstream Timeout (Edgio) 486 | The request failed to propagate between Edgio edge and 487 | the global POP. 488 | .It 544 Management Communication Error (Akamai EAA) 489 | The Login/Authentication POP cannot reach the 490 | management login manager. 491 | .It 544 Invalid Host Header (Edgio) 492 | The Host header is not a valid domain name. 493 | .It 545 Authentication Internal Error (Akamai EAA) 494 | The data POP cannot resolve/reach the authentication 495 | database. 496 | .It 545 Edgio Component Not Ready (Edgio) 497 | An unprepared Edgio component received traffic. 498 | .It 546 Unknown Application (Akamai EAA) 499 | The Login/Authentication POP does not have the 500 | application configuration. 501 | .It 546 Edgio Global POP TLS Error (Edgio) 502 | An error occurred negotiating a secure TLS connection 503 | with the Edgio global POP. 504 | .It 547 Edgio Global POP \&No HTTP Response (Edgio) 505 | No HTTP response from the global POP. 506 | .It 548 Invalid Response (Akamai EAA) 507 | The response received from the login server could not 508 | be validated via back-channel request from the cloud 509 | proxy to the login server. 510 | .It 548 Edgio Global POP DNS Resolution Error (Edgio) 511 | Failure to resolve the global POP's host name through 512 | the DNS. 513 | .It 549 Authentication Gateway Error (Akamai EAA) 514 | The Login service cannot reach directories to complete 515 | the authentication process. 516 | .It 552 Application Unreachable (Akamai EAA) 517 | The application service is not reachable from 518 | connector. 519 | .It 553 Directory Service Error (Akamai EAA) 520 | A directory service error during Kerberos 521 | authentication. 522 | .It 554 Authentication Token Error (Akamai EAA) 523 | The Kerberos token is not accepted by application. 524 | .It 555 Application does not support Kerberos (Akamai EAA) 525 | No negotiate option found in 401 challenge. 526 | .It 556 Unexpected Authentication Challenge (Akamai EAA) 527 | Encountered a 401 challenge on a URI not configured as 528 | login URI. 529 | .It 557 KDC Unreachable (Akamai EAA) 530 | The KDC is unreachable. 531 | .It 558 Connection Limit Stop: Service Concurrent Connections Exceeded (Akamai EAA) 532 | Too many concurrent connections. 533 | .It 559 Connection Limit Stop: Service Concurrent Connections Exceeded (Akamai EAA) 534 | Too many requests per second. 535 | .It 561 Invalid NTLM Challenge (Akamai EAA) 536 | The connector received an invalid NTLM challenge from 537 | server. 538 | .It 561 Unauthorized (AWS ELB) 539 | IdP could not authenticate the user. 540 | .It 562 Credential Error (Akamai EAA) 541 | Unable to encrypt or decrypt NTLM credentials. 542 | .It 598 Network Read Timeout Error 543 | Used by some HTTP proxies to signal a network read 544 | timeout behind the proxy to a client in front of the 545 | proxy. 546 | .It 599 Network Connect Timeout Error 547 | Used by some HTTP proxies to signal a network connect 548 | timeout behind the proxy to a client in front of the 549 | proxy. 550 | .It 600 (Akamai) 551 | Used by Akamai to indicate various invalid headers. 552 | .It 783 Unexpected Token (Shopify) 553 | The request includes a JSON syntax error. 554 | .It 893 (Edgio) 555 | Used by Edgio when load balancing high volume traffic 556 | for a specific asset within a POP. 557 | .El 558 | .Sh SEE ALSO 559 | RFC2324, 560 | RFC2518, 561 | RFC2616, 562 | RFC3229, 563 | RFC4918, 564 | RFC5842, 565 | RFC6585, 566 | RFC7230, 567 | RFC7231, 568 | RFC7232, 569 | RFC7233, 570 | RFC7538, 571 | RFC7540 572 | .Pp 573 | https://en.wikipedia.org/wiki/List_of_HTTP_status_codes 574 | .Sh HISTORY 575 | This list of HTTP status codes was originally compiled 576 | into a manual page by 577 | .An Jan Schaumann 578 | .Aq jschauma@netmeister.org 579 | in July 2021. 580 | -------------------------------------------------------------------------------- /httpstatus.7.pdf: -------------------------------------------------------------------------------- https://raw.githubusercontent.com/jschauma/httpstatus/bbebe7b86570daa95f966fe951e1eaa94855dd4c/httpstatus.7.pdf -------------------------------------------------------------------------------- /httpstatus.7.txt: -------------------------------------------------------------------------------- 1 | httpstatus(7) NetBSD Miscellaneous Information Manual httpstatus(7) 2 | 3 | NAME 4 | httpstatus -- HTTP status codes 5 | 6 | DESCRIPTION 7 | This manual page documents the HTTP status codes commonly issued by a web 8 | server in response to a client request. The status codes in this manual 9 | page are based on the information found in RFC7231 unless otherwise 10 | noted. 11 | 12 | HTTP status codes fall into one of five classes, identified by the first 13 | digit as follows: 14 | 15 | 1xx (Informational) 16 | The request was received, continuing process. 17 | 18 | 2xx (Successful) 19 | The request was successfully received, understood, and accepted. 20 | 21 | 3xx (Redirection) 22 | Further action needs to be taken in order to complete the request. 23 | 24 | 4xx (Client Error) 25 | The request contains bad syntax or cannot be fulfilled. 26 | 27 | 5xx (Server Error) 28 | The server failed to fulfill an apparently valid request. 29 | 30 | 1xx STATUS CODES 31 | 100 Continue 32 | The server has received the initial part of the request and the 33 | client should proceed to send the remainder. 34 | 35 | 101 Switching Protocols 36 | The server agrees to the client's request to switch protocols via the 37 | RFC7230 "Upgrade" header. 38 | 39 | 102 Processing 40 | The server has has accepted the complete request, but has not yet 41 | completed it. (WebDAV; RFC2518) 42 | 43 | 103 Early Hints 44 | The server is likely to send a final response with the header fields 45 | included in the informational response. (RFC8297) 46 | 47 | 2xx STATUS CODES 48 | 200 Ok 49 | The request has succeeded. 50 | 51 | 201 Created 52 | The request has been fulfilled and has resulted in one or more new 53 | resources being created. 54 | 55 | 202 Accepted 56 | The request has been accepted for processing, but the processing has 57 | not been completed. 58 | 59 | 203 Non-Authoritative Information 60 | The request was successful but the enclosed payload has been modified 61 | from that of the origin server's 200 (OK) response by a transforming 62 | proxy. 63 | 64 | 204 No Content 65 | The server has successfully fulfilled the request; there is no addi- 66 | tional content to send in the response payload body. 67 | 68 | 205 Reset Content 69 | The server has fulfilled the request; the client should reset its 70 | document view. 71 | 72 | 206 Partial Content 73 | The server is successfully fulfilling a range request for the target 74 | resource based on the client's "Range" header. (RFC7233) 75 | 76 | 207 Multi-Status 77 | Multiple resources were to be affected by the COPY, but errors on 78 | some of them prevented the operation from taking place. (WebDAV; 79 | RFC4918) 80 | 81 | 208 Already Reported 82 | Indicates that members of multiple bindings from a previous multi- 83 | status response are not repeated. (WebDAV; RFC5842) 84 | 85 | 226 IM Used 86 | The server has fulfilled a GET request for the resource, and the 87 | response is a representation of the result of one or more instance- 88 | manipulations applied to the current instance. (RFC3229) 89 | 90 | 3xx STATUS CODES 91 | 300 Multiple Choices 92 | The target resource has more than one representation which the client 93 | may choose from via Content Negotiation. 94 | 95 | 301 Moved Permanently 96 | The target resource has been assigned a new permanent URI and any 97 | future references to this resource ought to use one of the enclosed 98 | URIs. 99 | 100 | 302 Found 101 | The target resource resides temporarily under a different URI. 102 | 103 | 303 See Other 104 | The server is redirecting the user agent to a different resource, as 105 | indicated by a URI in the Location header field. 106 | 107 | 304 Not Modified 108 | A conditional GET or HEAD request has been received and would have 109 | resulted in a 200 (OK) response if it were not for the fact that the 110 | condition evaluated to false. (RFC7232) 111 | 112 | 305 Use Proxy 113 | The requested resource MUST be accessed through the proxy given by 114 | the Location field. (RFC2616) Deprecated due to security concerns 115 | regarding in-band configuration of a proxy. 116 | 117 | 306 Switch Proxy 118 | No longer used. Originally generated by a proxy server to indicate 119 | that the client or proxy should use the information in the accompany- 120 | ing 'Set- proxy' header to choose a proxy for subsequent requests. 121 | 122 | 307 Temporary Redirect 123 | The target resource resides temporarily under a different URI and the 124 | user agent MUST NOT change the request method if it performs an auto- 125 | matic redirection to that URI. 126 | 127 | 308 Permanent Redirect 128 | The target resource has been assigned a new permanent URI and any 129 | future references to this resource ought to use one of the enclosed 130 | URIs. (RFC7538) 131 | 132 | 4xx STATUS CODES 133 | 400 Bad Request 134 | The server cannot or will not process the request due to something 135 | that is perceived to be a client error (e.g., malformed request syn- 136 | tax, invalid request message framing, or deceptive request routing). 137 | 138 | 401 Unauthorized 139 | The request has not been applied because it lacks valid authentica- 140 | tion credentials for the target resource. 141 | 142 | 402 Payment Required 143 | Reserved for future use. 144 | 145 | 403 Forbidden 146 | The server understood the request but refuses to authorize it. 147 | 148 | 404 Not Found 149 | The origin server did not find a current representation for the tar- 150 | get resource or is not willing to disclose that one exists. 151 | 152 | 405 Method Not Allowed 153 | The method received in the request-line is known by the origin server 154 | but not supported by the target resource. 155 | 156 | 406 Not Acceptable 157 | The target resource does not have a current representation that would 158 | be acceptable to the user agent, such as due to the client's "Accept" 159 | header. 160 | 161 | 407 Proxy Authentication Required 162 | The client needs to authenticate itself in order to use a proxy. 163 | (RFC7235) 164 | 165 | 408 Request Timeout 166 | The server did not receive a complete request message within the time 167 | that it was prepared to wait. 168 | 169 | 409 Conflict 170 | The request could not be completed due to a conflict with the current 171 | state of the target resource. 172 | 173 | 410 Gone 174 | Access to the target resource is no longer available at the origin 175 | server; this condition is likely to be permanent. 176 | 177 | 411 Length Required 178 | The server refuses to accept the request without a defined Content- 179 | Length. 180 | 181 | 412 Precondition Failed 182 | One or more conditions given in the request header fields evaluated 183 | to false when tested on the server. (RFC7232) 184 | 185 | 413 Payload Too Large 186 | The server is refusing to process a request because the request pay- 187 | load is larger than the server is willing or able to process. 188 | 189 | 414 URI Too Long 190 | The server is refusing to service the request because the request- 191 | target is longer than the server is willing to interpret. 192 | 193 | 415 Unsupported Media Type 194 | The origin server is refusing to service the request because the pay- 195 | load is in a format not supported by this method on the target 196 | resource. 197 | 198 | 416 Range Not Satisfiable 199 | None of the ranges in the request's Range header field overlap the 200 | current extent of the selected resource or the set of ranges 201 | requested has been rejected due to invalid ranges or an excessive 202 | request of small or overlapping ranges. (RFC7233) 203 | 204 | 417 Expectation Failed 205 | The expectation given in the request's Expect header field could not 206 | be met by at least one of the inbound servers. 207 | 208 | 418 I'm a teapot 209 | An attempt to brew coffee was made, even though the target is a 210 | teapot. (RFC2324) 211 | 212 | 421 Misdirected Request 213 | The request was directed at a server that is not able to produce a 214 | response. (RFC7540) 215 | 216 | 422 Unprocessable Entity 217 | The server understands the content type of the request entity and the 218 | syntax of the request entity is correct, but was unable to process 219 | the contained instructions. (WebDAV; RFC4918) 220 | 221 | 423 Locked 222 | The source or destination resource of a method is locked. (WebDAV; 223 | RFC4918) 224 | 225 | 424 Failed Dependency 226 | The method could not be performed on the resource because the 227 | requested action depended on another action and that action failed. 228 | (WebDAV; RFC4918) 229 | 230 | 425 Too Early 231 | The server is unwilling to risk processing a request that might be 232 | replayed. (RFC8470) 233 | 234 | 426 Upgrade Required 235 | The server refuses to perform the request using the current protocol 236 | but might be willing to do so after the client upgrades to a differ- 237 | ent protocol. 238 | 239 | 428 Precondition Required 240 | The origin server requires the request to be conditional. (RFC6585) 241 | 242 | 429 Too Many Requests 243 | The user has sent too many requests in a given amount of time. 244 | (RFC6585) 245 | 246 | 431 Request Header Fields Too Large 247 | The server is unwilling to process the request because its header 248 | fields are too large. (RFC6585) 249 | 250 | 451 Unavailable For Legal Reasons 251 | The server is denying access to the resource as a consequence of a 252 | legal demand. (RFC7725) Named after Ray Bradbury's "Fahrenheit 451". 253 | 254 | 5xx STATUS CODES 255 | 500 Internal Server Error 256 | The server encountered an unexpected condition that prevented it from 257 | fulfilling the request. 258 | 259 | 501 Not Implemented 260 | The server does not support the functionality required to fulfill the 261 | request. 262 | 263 | 502 Bad Gateway 264 | The server, while acting as a gateway or proxy, received an invalid 265 | response from an inbound server it accessed while attempting to ful- 266 | fill the request. 267 | 268 | 503 Service Unavailable 269 | The server is currently unable to handle the request due to a tempo- 270 | rary overload or scheduled maintenance, which will likely be allevi- 271 | ated after some delay. 272 | 273 | 504 Gateway Timeout 274 | The server, while acting as a gateway or proxy, did not receive a 275 | timely response from an upstream server it needed to access in order 276 | to complete the request. 277 | 278 | 505 HTTP Version Not Supported 279 | The server does not support, or refuses to support, the major version 280 | of HTTP that was used in the request message. 281 | 282 | 506 Variant Also Negotiates 283 | The server's chosen variant resource is configured to engage in 284 | transparent content negotiation itself, and is therefore not a proper 285 | end point in the negotiation process. (RFC2295) 286 | 287 | 507 Insufficient Storage 288 | The method could not be performed on the resource because the server 289 | is unable to store the representation needed to successfully complete 290 | the request. (WebDAV; RFC4918) 291 | 292 | 508 Loop Detected 293 | The server terminated an operation because it encountered an infinite 294 | loop while processing a request with "Depth: infinity". (WebDAV; 295 | RFC5842) 296 | 297 | 510 Not Extended 298 | The policy for accessing the resource has not been met in the 299 | request. (RFC2774) 300 | 301 | 511 Network Authentication Required 302 | The client needs to authenticate to gain network access. (RFC6585) 303 | 304 | NON STANDARD HTTP STATUS CODES 305 | In addition to the above, several HTTP server or proxy implementations 306 | include custom status codes, particularly in the 4xx and 5xx classes. 307 | 308 | 000 (AWS ELB) 309 | Used by AWS Elastic Load Balancing with HTTP/2 GOAWAY frame if the 310 | compressed length of any of the headers exceeds 8K bytes or if more 311 | than 10K requests are served through one connection exceeds 10,000. 312 | 313 | 000 (curl) 314 | Used by curl(1) to indicate a failed execution. 315 | 316 | 000 Client-Side Abort (Akamai LDS) 317 | Used by Akamai Log Delivery Services if a download was terminated by 318 | the end-user before the edge server is able to send back the response 319 | header. 320 | 321 | 000 (Looker Studio) 322 | No HTTP code was received. 323 | 324 | 218 This is fine (Apache httpd) 325 | A catch-all error condition displayed instead of a 4xx or 5xx error, 326 | allowing the passage of message bodies through the server when the 327 | ProxyErrorOverride setting is enabled. 328 | 329 | 299 Deprecated (Linode) 330 | The request was successful, but involved a deprecated endpoint. 331 | 332 | 419 Page Expired (Laravel) 333 | A CSRF Token is missing, expired, or cannot be verified. 334 | 335 | 430 Shopify Security Rejection (Shopify) 336 | The request was deemed malicious. 337 | 338 | 440 Login Time-out (Microsoft IIS) 339 | The client's session has expired and must log in again. 340 | 341 | 444 No Response (nginx) 342 | Used by the ngx_http_rewrite_module to instruct the server to close 343 | the connection without sending a response header. 344 | 345 | 449 Retry With Status Code (Microsoft IIS) 346 | The request cannot be satisfied because insufficient information was 347 | provided by the client. 348 | 349 | 450 Blocked by Windows Parental Controls (Microsoft) 350 | Windows Parental Controls are turned on and are blocking access to 351 | the requested webpage. 352 | 353 | 451 Redirect (Microsoft Exchange) 354 | Used by Microsoft Exchange ActiveSync to indicate that the client is 355 | attempting to connect to the wrong server, or if there is a more 356 | efficient server to use to reach the user's mailbox 357 | 358 | 460 (AWS ELB) 359 | The client closed the connection with the load balancer before the 360 | idle timeout period elapsed. 361 | 362 | 462 Not Allowed (Fastly) 363 | The client's IP was blocked. 364 | 365 | 463 (AWS ELB) 366 | The load balancer received an X-Forwarded-For request header with too 367 | many IP addresses. 368 | 369 | 464 (AWS ELB) 370 | Incompatible protocol versions between the client and the origin 371 | server. 372 | 373 | 492 User Access Forbidden (Akamai EAA) 374 | The client is not authorized to access the application. 375 | 376 | 493 Unsupported Browser (Akamai EAA) 377 | The client did not send a Server Name Identification (SNI) in the TLS 378 | handshake. 379 | 380 | 494 Request Header Too Large (nginx) 381 | The client sent too large a request or too long a header line. 382 | 383 | 494 Request Header Or Cookie Too Large (Akamai EAA) 384 | An HTTP Request Header is bigger than the configured buffer value. 385 | 386 | 498 Invalid Token (Esri) 387 | Used by the Esri ArcGIS Server to indicate an expired or otherwise 388 | invalid token. 389 | 390 | 495 SSL Certificate Error (nginx) 391 | The client has provided an invalid client certificate. 392 | 393 | 496 496 SSL Certificate Required (nginx) 394 | A client certificate is required but was not provided. 395 | 396 | 497 HTTP Request Sent to HTTPS Port (nginx) 397 | The client has made an HTTP request to an HTTPS port. 398 | 399 | 499 Client Closed Request (nginx) 400 | The client has closed the request before the server could send a 401 | response. 402 | 403 | 499 Token Required (Esri) 404 | Used by the Esri ArcGIS Server to indicate that a token is required 405 | but was not submitted. 406 | 407 | 503 Loop Detected (Fastly) 408 | A request appears to originate from the same Fastly service that it 409 | is trying to invoke, or the request has transited too many Fastly 410 | servers. 411 | 412 | 509 Bandwidth Limit Exceeded (Apache httpd / cPanel) 413 | The server has exceeded the bandwidth specified by the server admin- 414 | istrator. 415 | 416 | 520 Web Server Returned an Unknown Error (Cloudflare) 417 | The origin server returned an empty, unknown, or unexpected response 418 | to Cloudflare. 419 | 420 | 521 Web Server Is Down (Cloudflare) 421 | The origin server refused connections. 422 | 423 | 522 Connection Timed Out (Cloudflare) 424 | Time out when contacting the origin server. 425 | 426 | 523 Origin Is Unreachable (Cloudflare) 427 | The origin server was unreachable. 428 | 429 | 524 A Timeout Occurred (Cloudflare) 430 | After a successful TCP connection to the origin server the HTTP 431 | response timed out. 432 | 433 | 525 SSL Handshake Failed (Cloudflare) 434 | TLS handshake failure with the origin server. 435 | 436 | 526 Invalid SSL Certificate (Cloudflare / Cloud Foundry) 437 | Unable to validate the origin server's TLS certificate. 438 | 439 | 527 Railgun Error (Cloudflare) 440 | Connection interrupted between Cloudflare and the origin server's 441 | Railgun server. 442 | 443 | 529 Site is overloaded (Qualys SSLabs) 444 | API service is overloaded. 445 | 446 | 530 Internal Edgio Error (Edgio) 447 | An unexpected error. 448 | 449 | 530 (Cloudflare) 450 | Used by Cloudflare as a generic error status code. More details can 451 | be found in the accompanying HTML body describing a 1XXX error code. 452 | 453 | 530 Site is frozen (Pantheon) 454 | A site that has been frozen due to inactivity. 455 | 456 | 530 Origin DNS Error (Shopify) 457 | Cloudflare can't resolve the requested DNS record. 458 | 459 | 531 Project Upstream Connection Error (Edgio) 460 | Unable to establish a connection to the origin server. 461 | 462 | 532 Project Response Too Large (Edgio) 463 | A returned a response size was greater than the allowed maximum. 464 | 465 | 533 Project Upstream TLS Error (Edgio) 466 | Unable to establish a TLS connection to the origin. 467 | 468 | 534 Project Error (Edgio) 469 | The project's serverless code has failed unexpectedly or has issued a 470 | malformed response. 471 | 472 | 535 Unknown Project (Edgio) 473 | Missing or mismatching Host header. 474 | 475 | 536 Project HTTP Response Timeout (Edgio) 476 | Time out when contacting the origin server. 477 | 478 | 537 Project DNS Resolution Error (Edgio) 479 | The proxy was unable to resolve the host name. 480 | 481 | 538 Project Request Loop (Edgio) 482 | The request went through too many Edgio servers. 483 | 484 | 539 Project Timeout (Edgio) 485 | The project's serverless code did not respond in time. 486 | 487 | 540 Temporarily Disabled (Shopify) 488 | The requested endpoint has been temporarily disabled. 489 | 490 | 540 Connectivity Disrupted (Akamai EAA) 491 | The connector does not have dial-out connections to either the data 492 | POP for the application or access to the directory. 493 | 494 | 540 Out of Memory (Edgio) 495 | The project's serverless code caused an out-of-memory situation. 496 | 497 | 541 Edgio Out of Workers (Edgio) 498 | Traffic was too high to be scheduled for processing within the sched- 499 | uling timeout. 500 | 501 | 542 Internal Database Error (Akamai EAA) 502 | The data POP cannot reach the authentication database. 503 | 504 | 542 Project Header Overflow (Edgio) 505 | The project's request or response had too many HTTP headers. 506 | 507 | 543 IdP Communication Error (Akamai EAA) 508 | The data POP cannot reach the IdP or directory service. 509 | 510 | 543 Global Upstream Timeout (Edgio) 511 | The request failed to propagate between Edgio edge and the global 512 | POP. 513 | 514 | 544 Management Communication Error (Akamai EAA) 515 | The Login/Authentication POP cannot reach the management login man- 516 | ager. 517 | 518 | 544 Invalid Host Header (Edgio) 519 | The Host header is not a valid domain name. 520 | 521 | 545 Authentication Internal Error (Akamai EAA) 522 | The data POP cannot resolve/reach the authentication database. 523 | 524 | 545 Edgio Component Not Ready (Edgio) 525 | An unprepared Edgio component received traffic. 526 | 527 | 546 Unknown Application (Akamai EAA) 528 | The Login/Authentication POP does not have the application configura- 529 | tion. 530 | 531 | 546 Edgio Global POP TLS Error (Edgio) 532 | An error occurred negotiating a secure TLS connection with the Edgio 533 | global POP. 534 | 535 | 547 Edgio Global POP No HTTP Response (Edgio) 536 | No HTTP response from the global POP. 537 | 538 | 548 Invalid Response (Akamai EAA) 539 | The response received from the login server could not be validated 540 | via back-channel request from the cloud proxy to the login server. 541 | 542 | 548 Edgio Global POP DNS Resolution Error (Edgio) 543 | Failure to resolve the global POP's host name through the DNS. 544 | 545 | 549 Authentication Gateway Error (Akamai EAA) 546 | The Login service cannot reach directories to complete the authenti- 547 | cation process. 548 | 549 | 552 Application Unreachable (Akamai EAA) 550 | The application service is not reachable from connector. 551 | 552 | 553 Directory Service Error (Akamai EAA) 553 | A directory service error during Kerberos authentication. 554 | 555 | 554 Authentication Token Error (Akamai EAA) 556 | The Kerberos token is not accepted by application. 557 | 558 | 555 Application does not support Kerberos (Akamai EAA) 559 | No negotiate option found in 401 challenge. 560 | 561 | 556 Unexpected Authentication Challenge (Akamai EAA) 562 | Encountered a 401 challenge on a URI not configured as login URI. 563 | 564 | 557 KDC Unreachable (Akamai EAA) 565 | The KDC is unreachable. 566 | 567 | 558 Connection Limit Stop: Service Concurrent Connections Exceeded 568 | (Akamai EAA) 569 | Too many concurrent connections. 570 | 571 | 559 Connection Limit Stop: Service Concurrent Connections Exceeded 572 | (Akamai EAA) 573 | Too many requests per second. 574 | 575 | 561 Invalid NTLM Challenge (Akamai EAA) 576 | The connector received an invalid NTLM challenge from server. 577 | 578 | 561 Unauthorized (AWS ELB) 579 | IdP could not authenticate the user. 580 | 581 | 562 Credential Error (Akamai EAA) 582 | Unable to encrypt or decrypt NTLM credentials. 583 | 584 | 598 Network Read Timeout Error 585 | Used by some HTTP proxies to signal a network read timeout behind the 586 | proxy to a client in front of the proxy. 587 | 588 | 599 Network Connect Timeout Error 589 | Used by some HTTP proxies to signal a network connect timeout behind 590 | the proxy to a client in front of the proxy. 591 | 592 | 600 (Akamai) 593 | Used by Akamai to indicate various invalid headers. 594 | 595 | 783 Unexpected Token (Shopify) 596 | The request includes a JSON syntax error. 597 | 598 | 893 (Edgio) 599 | Used by Edgio when load balancing high volume traffic for a specific 600 | asset within a POP. 601 | 602 | SEE ALSO 603 | RFC2324, RFC2518, RFC2616, RFC3229, RFC4918, RFC5842, RFC6585, RFC7230, 604 | RFC7231, RFC7232, RFC7233, RFC7538, RFC7540 605 | 606 | https://en.wikipedia.org/wiki/List_of_HTTP_status_codes 607 | 608 | HISTORY 609 | This list of HTTP status codes was originally compiled into a manual page 610 | by Jan Schaumann in July 2021. 611 | 612 | NetBSD 9.3 December 14, 2023 NetBSD 9.3 613 | --------------------------------------------------------------------------------