303 See Other Error
Contents |
referer DNT X-Forwarded-For Status codes 301 Moved Permanently 302 Found 303 See Other 403 Forbidden 404 Not Found 451 Unavailable For Legal Reasons v t e This is a list of Hypertext Transfer Protocol (HTTP) response status
303 Error Hard Drive
codes. It includes codes from IETF internet standards, other IETF RFCs, other specifications, and some 303 error code hp additional commonly used codes. The first digit of the status code specifies one of five classes of response; an HTTP client
Error 303 Text Message
must recognise these five classes at a minimum. The phrases used are the standard wordings, but any human-readable alternative can be provided. Unless otherwise stated, the status code is part of the HTTP/1.1 standard (RFC 7231).[1] error 303 windows 7 The Internet Assigned Numbers Authority (IANA) maintains the official registry of HTTP status codes.[2] Microsoft IIS sometimes uses additional decimal sub-codes to provide more specific information,[3] but not all of those are here (note that these sub-codes only appear in the response payload and in documentation; not in the place of an actual HTTP status code). Contents 1 1xx Informational 2 2xx Success 3 3xx Redirection 4 4xx Client Error 5 kcferrordomaincfnetwork error 303 5xx Server Error 6 Unofficial codes 6.1 Internet Information Services 6.2 nginx 6.3 CloudFlare 7 See also 8 Notes 9 References 10 External links 1xx Informational[edit] Request received, continuing process. This class of status code indicates a provisional response, consisting only of the Status-Line and optional headers, and is terminated by an empty line. Since HTTP/1.0 did not define any 1xx status codes, servers must not[note 1] send a 1xx response to an HTTP/1.0 client except under experimental conditions.[4] 100 Continue The server has received the request headers and the client should proceed to send the request body (in the case of a request for which a body needs to be sent; for example, a POST request). Sending a large request body to a server after a request has been rejected for inappropriate headers would be inefficient. To have a server check the request's headers, a client must send Expect: 100-continue as a header in its initial request and receive a 100 Continue status code in response before sending the body. The response 417 Expectation Failed indicates the request should not be continued.[2] 101 Switching Protocols The requester has asked the server to switch protocols and the server has agreed to do so.[5] 102 Processing (WebDAV; RFC 2518) A WebDAV request may contain
that the response to the request can be found at the specified
Error 303 Icon Is Missing From Package
URL, and should be retrieved from there. It does not error 303 eso mean that something has moved - it is simply specifying the address at which the response
Http/1.1 303 See Other
to the request can be found. Why it Occurs The HTTP status code 303 See Other is the correct manner to in which to redirect web applications https://en.wikipedia.org/wiki/List_of_HTTP_status_codes to a new URL, particularly after an HTTP POST has been performed.This response indicates that the correct response can be found under a different URL and should be retrieved using a GET method. The specified URL is not a substitute reference for the original resource. Fixing 303 Error Code The 303 response MUST http://100pulse.com/http-statuscode/303.jsp NOT be cached, but the response to the second (redirected) request might be cacheable. The different URL SHOULD be given by the Location field in the response. Unless the request method was HEAD, the entity of the response SHOULD contain a short hypertext note with a hyperlink to the new URL(s). If you monitor your website through 100 pulse, we will intimate you through mail or short message service whenever you encounter 303 status code. Features Website Monitoring Monitor DNS Server Mail Server Monitoring Mysql Server Monitoring FTP Monitoring Port Monitoring Alerts & Reports Instant Notification Web Server Monitoring Report Public Report Template Free Uptime Button Monitoring Tools Webpage Availability Checker Port checker DNS Checker IP Finder Server location Finder and more... Reseller Affiliate Program Pricing Latest Updates Feedback Write a testimonial About Us Contact Us Follow Us on Twitter Facebook Server Time : 29-Sep-2016 22:26:33 GMT All Rights reserved © 100pulse.com Terms | Privacy | Sitemap
to the original request. A user agent can perform a retrieval request targeting that URI (a GET or HEAD https://httpstatuses.com/303 request if using HTTP), which might also be redirected, and present http://serverfault.com/questions/391181/examples-of-302-vs-303 the eventual result as an answer to the original request. Note that the new URI in the Location header field is not considered equivalent to the effective request URI. This status code is applicable to any HTTP method. It is primarily used to allow error 303 the output of a POST action to redirect the user agent to a selected resource, since doing so provides the information corresponding to the POST response in a form that can be separately identified, bookmarked, and cached, independent of the original request. A 303 response to a GET request indicates that the origin server does 303 see other not have a representation of the target resource that can be transferred by the server over HTTP. However, the Location field value refers to a resource that is descriptive of the target resource, such that making a retrieval request on that other resource might result in a representation that is useful to recipients without implying that it represents the original target resource. Note that answers to the questions of what can be represented, what representations are adequate, and what might be a useful description are outside the scope of HTTP. Except for responses to a HEAD request, the representation of a 303 response ought to contain a short hypertext note with a hyperlink to the same URI reference provided in the Location header field. Source: RFC7321 Section 6.4.4 303 Code References Rails HTTP Status Symbol :see_other Go HTTP Status Constant http.StatusSeeOther Symfony HTTP Status Constant Response::HTTP_SEE_OTHER Python2 HTTP Status Constant httplib.SEE_OTHER Python3+ HTTP Status Constant http.client.SEE_OTHER Python3.5+ HTTP Status Constant http.HTTPStatus.SEE_OTHER← Return to httpstatuses.com
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Server Fault Questions Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top Examples of 302 vs 303 up vote 12 down vote favorite 2 What is the difference between a 302 and 303 response? http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html 10.3.3 302 Found 10.3.4 303 See Other Are these interchangeable or why would one be used over the other? Could you please provide a use case of when one would be used (and the other would not) ? http redirect share|improve this question edited May 21 '12 at 19:38 asked May 21 '12 at 19:38 David542 32139 add a comment| 3 Answers 3 active oldest votes up vote 16 down vote accepted The description on the page to which you linked seem to be fairly descriptive of their intended purpose: A 302 redirect indicates that the redirect is temporary -- clients should check back at the original URL in future requests. A 303 redirect is meant to redirect a POST request to a GET resource (otherwise, the client assumes that the request method for the new location is the same as for the original resource). If you're redirecting a client as part of your web application but expect them to always start at the web application (for example, a URL shortener), a 302 redirect seems to make sense. A 303 redirect is for use when you are receiving POST data from a client (e.g., a form submission) and you want to redirect them to a new web page to be retrieved using GET instead of POST (e.g., a standard page request). But see this note from the status code definitions -- most clients will do the same thing for either a 302 or 303: Note: RFC 1945 and RFC 2068 specify that the client is not allowed to change the method on the redirected request. However, most existing user agent implementations treat 302 as if it were a 303 response, performing a GET on the Locat