Home
Tools

Sign In / Create an Account

REST & WOA Wiki

Articles

Frameworks

Glossary

HTTP Headers

HTTP Methods

HTTP Status Codes
- 100 - Continue
- 101 - Switching Protocols
- 200 - OK
- 201 - Created
- 202 - Accepted
- 203 - Non-Authoritative Information
- 204 - No Content
- 205 - Reset Content
- 206 - Partial Content
- 207 - Multi-Status
- 300 - Multiple Choices
- 301 - Moved Permanently
- 302 - Found
- 303 - See Other
- 304 - Not Modified
- 305 - Use Proxy
- 306 - (Reserved)
- 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
- 408 - Request Timeout
- 409 - Conflict
- 410 - Gone
- 411 - Length Required
- 412 - Precondition Failed
- 413 - Request Entity Too Large
- 414 - Request-URI Too Long
- 415 - Unsupported Media Type
- 416 - Requested Range Not Satisfiable
- 417 - Expectation Failed
- 422 - Unprocessable Entity
- 423 - Locked
- 424 - Failed Dependency
- 500 - Internal Server Error
- 501 - Not Implemented
- 502 - Bad Gateway
- 503 - Service Unavailable
- 504 - Gateway Timeout
- 505 - HTTP Version Not Supported
- 507 - Insufficient Storage

Languages

RFC 2616 - Hypertext Transfer Protocol -- HTTP/1.1

RFC 4918 - HTTP Extensions for Web Distributed Authoring and Versioning (WebDAV)

TODOs

Work in Progress

Table of contents

Was this article helpful?

502 - Bad Gateway

Modified 21:30, 21 Jul 2008 by SteveB

Table of contents

No headers

The server, while acting as a gateway or proxy, received an invalid response from the upstream server it accessed in attempting to fulfill the request.

Was this article helpful?: Yes No
Page statistics: 1960 view(s) and 1 edit(s)
Social share: Share this page?

Tags

RFC2616

Comments

You must to post a comment.

Attachments