The Web Server and Website Monitoring Service, trusted by 48117 customers
HTTP Status Codes - 3xx
3xx - Redirection
The client must take additional action to complete the request. This group of status codes indicates that further action needs to be taken by the user agent in order to complete the request. The action required may be carried out by the user agent without interaction with the client only if the method used in the second request is GET or HEAD.
300 - Multiple Choices
The server responds with a 300 error message when the requested resource points to a destination with multiple representations, each with its own specific location, where the user has to select a preference and redirect its request to that location, so that the requested page (file) is displayed. In some cases, selection of the most appropriate choice can be made automatically.
301 - Moved Permanently
The server responds with a 301 error message when the requested resource has been assigned a new permanent URL. Usually the server response contains a reference to the new URL where the resource was moved. If it is applicable, WebSitePulse monitoring agent will follow automatic redirections with up to 10 redirects from the original requested URL.
302 - Found (Moved Temporarily)
The server responds with a 302 error message when the requested resource has been temporarily moved to a different URL. Usually the server response contains a reference to the new URL where the resource was moved. Clients should continue to use the request URL since the redirection might be altered on occasion. This is one of the most popular redirect codes and the original describing phrase was "Moved Temporarily", but popular browsers implemented it as a 303 - See Other code. Therefore, HTTP/1.1 added status codes 303 and 307 to make more clear the two behaviors. However, some of Web applications and frameworks still use the 302 status code as if it were the 303. If applicable, WebSitePulse monitoring agent will follow automatic redirections with up to 10 redirects from the original requested URL.
303 - See Other
A web server responds with this status code when the requested resource can be found under a different URL. The server response contains a reference to the URL where the requested resource is, and the user agent or the WebSitePulse monitoring agent should retrieve the information using GET method request. The new URL is not a substitute reference for the originally requested resource.
304 - Not Modified
A web server responds with this status code when the user agent sends conditional Get request and access is allowed, but the contents of the requested web page have not been modified since the browser last downloaded it or cached it. Search engines need this information to determine if there are any changes in particular URL contents.
You should not receive this status message neither with the WebSitePulse monitoring system nor using a common web browser. If the web page has not been modified, your browser should take it from the cache and display it. Our user agent request does not allow this status code.
305 - Use Proxy
This is a very rare server status message. The requested resource should be accessed through a proxy. The URL of the proxy should be given in the response. The recipient is then expected to repeat the request via the proxy. Sometimes 305 statuses are seen on web sites that restrict access to certain content to valid users coming through a proxy server.
You should never actually see this message, as your web browser should redirect you immediately to the given URL. If the URL is not known through the response, there must be a problem with the Web server or the redirection is not set up properly.
306 - Switch Proxy (Unused)
The 306 status code was used in a previous version of the specification, but is no longer used and currently the code is reserved.
307 - Temporary Redirect
With this response a web server informs the client that the requested URL resides temporarily under a different URL. The new temporary URL should be given in the response from the server. The recipient is expected to follow the redirection but future requests can still be directed to the original URL. In contrast to the 303 code, the original POST request must be repeated with another POST request.
You should never actually see this message, as your web browser should redirect you immediately to the given URL. Our system will report this status message either if no alternative URL is given in the server response or the number of redirections exceeds 10 (this limitation intends to prevent the monitoring agent to enter into an infinite loop).