The Web server (running the Web site) thinks that the HTTP data stream sent from the client (e.g. your Web browser or our CheckUpDown robot) was correct, but access to the URL resource requires the prior use of a proxy server that needs some authentication which has not been provided. This typically means you must log in (enter user ID and password) with the proxy server first.
A 407 error detected via a Web browser can often be resolved by navigating to the URL in a slightly different way e.g. accessing another URL for the proxy server first. Your ISP should be able to explain the role of the proxy server in their security setup and how you should use it.
This code is similar to 401 - Unauthorized, but indicates that the client should first authenticate with a proxy server. The same discussion applies to error 407 as to error 401, except that an additional proxy server is involved for 407.
Our service monitors your site for HTTP errors like 407. Because they indicate fundamental authority problems, we can only resolve 407 errors you see on your CheckUpDown account by negotiation with the personnel responsible for security on and around the Web site and any proxy servers. These discussions unfortunately may take some time, but can often be amicably resolved. You can assist by endorsing our service to the security personnel. Please contact us (email preferred) if you see persistent 407 errors, so that we can agree the best way to resolve them.
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with the Web server:
This error occurs in the final step above when the client receives an HTTP status code that it recognises as '407'.