If the response could be unacceptable, a user agent SHOULD temporarily stop receipt of more data and query the user for a decision on further actions. 10.4.8 407 Proxy Authentication Required This code is similar to 401 (Unauthorized), but indicates that the client must first authenticate itself with the proxy. a Web accelerator) that received a 200 OK from its origin, but is returning a modified version of the origin's response. 204 No Content The server successfully processed the request and is not returning any content. 205 Reset Content The server successfully processed the request, but is not returning any content. Unless otherwise stated, the status code is part of the HTTP/1.1 standard (RFC 7231). The Internet Assigned Numbers Authority (IANA) maintains the official registry of HTTP status codes. Microsoft IIS sometimes uses additional decimal sub-codes to provide more specific information, 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). Comment 2 (mostly gone) XtC4UaLL [:xtc4uall] 2010-04-24 03:38:26 PDT Is Bug 544979 related here? weblink
Since the redirection MAY be altered on occasion, the client SHOULD continue to use the Request-URI for future requests. Twitter. 2014. IETF. Perhaps there is a misspelling in the server name or the server no longer exists.
A client SHOULD detect infinite redirection loops, since such loops generate network traffic for each redirection. A user agent may automatically redirect a request. connect#failed_connect FTP Error 502 The FTP server server_name returned an error. 302 Police Code transcoding#unsupported Tunnel Connection Failed 502 Could not connect to the server hostname.
In this case, the response entity would likely contain a list of the differences between the two versions in a format defined by the response Content-Type. 10.4.11 410 Gone The requested resource is no longer available at the server and no forwarding address is known. Http 302 Vs 301 What I don't know is where the fix should be - should the stream loader have its OnStartRequest called by that point, or should it just pass the context from the channel (I haven't figured out why it's even stored yet). Authorization will not help and the request SHOULD NOT be repeated. More Bonuses timeout#activity No Response Header From Server 502 The host server_name did not return the document URL correctly.
If they do change, then this is typically because a redirection URL is being suggested. Http 301 Retrieved August 30, 2016. ^ Stewart, Mark; djna. "Create request with POST, which response codes 200 or 201 and content". This second condition should be fairly unlikely - and may indicate a recursive pattern e.g. If you can interpret the correct meaning of the http error code, you can decide the places to look at for resolving this issue.
These status codes are applicable to any request method. https://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html Check the location and try again. Http 302 Error Fix This error code is specific to IIS 6.0. 302 Moved Temporarily Fix This response is primarily intended to allow input for actions to take place without causing a change to the user agent's active document view, although any new or updated metainformation SHOULD be applied to the document currently in the user agent's active view.
The temporary URI SHOULD be given by the Location field in the response. have a peek at these guys External links RFC 2616 (HTTP 1.1) RFC 1945 (HTTP 1.0) Retrieved from "https://en.wikipedia.org/w/index.php?title=HTTP_302&oldid=732065033" Categories: Hypertext Transfer Protocol status codes Navigation menu Personal tools Not logged inTalkContributionsCreate accountLog in Namespaces Article Talk Variants Views Read Edit View history More Search Navigation Main pageContentsFeatured contentCurrent eventsRandom articleDonate to WikipediaWikipedia store Interaction HelpAbout WikipediaCommunity portalRecent changesContact page Tools What links hereRelated changesUpload fileSpecial pagesPermanent linkPage informationWikidata itemCite this page Print/export Create a bookDownload as PDFPrintable version Languages BoarischBahasa IndonesiaPortuguêsСрпски / srpskiУкраїнська中文 Edit links This page was last modified on 29 July 2016, at 10:43. These can provide additional information about the new URL(s) which the Web server thinks we should be accessing. Bad command or file name Halt and Catch Fire HTTP 418 Out of memory Lists List of HTTP status codes List of FTP server return codes Related Kill screen Spinning pinwheel Windows wait cursor Retrieved from "https://en.wikipedia.org/w/index.php?title=List_of_HTTP_status_codes&oldid=744546936" Categories: Hypertext Transfer Protocol status codesInternet-related listsHidden categories: All articles with unsourced statementsArticles with unsourced statements from July 2016Articles with unsourced statements from August 2016Commons category without a link on WikidataOfficial website missing URLUse mdy dates from November 2012 Navigation menu Personal tools Not logged inTalkContributionsCreate accountLog in Namespaces Article Talk Variants Views Read Edit View history More Search Navigation Main pageContentsFeatured contentCurrent eventsRandom articleDonate to WikipediaWikipedia store Interaction HelpAbout WikipediaCommunity portalRecent changesContact page Tools What links hereRelated changesUpload fileSpecial pagesPermanent linkPage informationWikidata itemCite this page Print/export Create a bookDownload as PDFPrintable version Languages العربيةČeštinaDeutschEspañolفارسیFrançais한국어Bahasa IndonesiaÍslenskaItalianoעבריתქართულიBahasa MelayuNederlands日本語Norsk bokmålPolskiPortuguêsРусскийСрпски / srpskiSvenskaไทยTürkçeУкраїнська中文 Edit links This page was last modified on 15 October 2016, at 23:22. Http 302 Redirect Example
https://tools.ietf.org/html/rfc2616#section-10.2.1. Http 200 Retrieved 16 October 2015. ^ a b c d Nottingham, M.; Fielding, R. (April 2012). "RFC 6585 – Additional HTTP Status Codes". Last Comment Bug561536 - HTTP CONNECT does not properly handle 302 error Summary: HTTP CONNECT does not properly handle 302 error Status: RESOLVED FIXED Whiteboard: Keywords: fixed220.127.116.11, regression Product: Core Classification: Components Component: Networking: HTTP (show other bugs) Version: Trunk Platform: All All Importance: -- normal with 1 vote (vote) TargetMilestone: mozilla1.9.3a5 Assigned To: Boris Zbarsky [:bz] (still a bit busy) QA Contact: TriageOwner: Patrick McManus [:mcmanus] Mentors: URL: https://www.dyndns.com/account/ Duplicates: 492459 (view as bug list) Depends on: 564081 Blocks: 491818 Show dependency tree /graph Reported: 2010-04-24 01:30 PDT by Ivan Modified: 2013-03-14 08:54 PDT (History) CC List: 12 users (show) asqueella ben.bucksch bugzilla bzbarsky cbiesinger gavin.sharp heiko leec100 mh+mozilla p.zaccaria reed xtc4uall Flags: bzbarsky: in-testsuite?
Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. The 304 response MUST NOT contain a message-body, and thus is always terminated by the first empty line after the header fields. Retrieved 16 October 2015. ^ "202". 302 Error Iis o 500.18 – URL authorization store cannot be opened.
By default, this queue is limited to 3000 requests. o 403.12 - Mapper denied access. Retrieved October 24, 2009. ^ "Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content, Section 6.4". this content connect#hangup Temporarily Moved 302 The document you requested, URL, has moved to a new location.