Search results
Results from the WOW.Com Content Network
This class of status code indicates the client must take additional action to complete the request. Many of these status codes are used in URL redirection. [2]A user agent may carry out the additional action with no user interaction only if the method used in the second request is GET or HEAD.
If the user does not provide valid credentials or if the authentication fails, a 403 status code is returned. IP restrictions: The server may also restrict access to specific IP addresses or IP ranges. If the user's IP address is not included in the list of permitted addresses, a 403 status code is returned.
Main page; Contents; Current events; Random article; About Wikipedia; Contact us; Help; Learn to edit; Community portal; Recent changes; Upload file
It should only contain pages that are Hypertext Transfer Protocol status codes or lists of Hypertext Transfer Protocol status codes, as well as subcategories containing those things (themselves set categories). Topics about Hypertext Transfer Protocol status codes in general should be placed in relevant topic categories
This page was last edited on 25 March 2005, at 11:40 (UTC).; Text is available under the Creative Commons Attribution-ShareAlike 4.0 License; additional terms may ...
From a code: This is a redirect from a code that has no distinctive category to which it may be sorted. Examples are DOCTYPE , and redirects from HTML and hexadecimal codes. To an embedded anchor : This is a redirect from a topic that does not have its own page to an embedded anchor on the redirect's target page.
There are also other roads named 401, see the List of highways numbered 401; 401(a), a type of U.S. tax-deferred retirement savings plan defined by a subsection of the Internal Revenue Code; 401(k), a type of U.S. employer-sponsored retirement plan defined by a subsection of the Internal Revenue Code; Titanic The hull number for RMS Titanic
[2] 451 provides more information than HTTP 403, which is often used for the same purpose. [3] This status code is currently a proposed standard in RFC 7725 but is not yet formally a part of HTTP, as of RFC 9110.