HTTP status codes

Codes starting with 2xx mean success, 3xx a redirect, 4xx a problem with the request, 5xx a failure on the server side. The most common are 200, 301, 403, 404, 429 and 502.

When working through a proxy, it is important to understand who responded. Code 407 comes from the proxy itself: it is a login issue. Code 403 or 429 is usually sent by the site: access is restricted or a rate limit was triggered.

Codes 502 and 503 can come both from the proxy and from the site. Explanations are collected on the proxy error codes page.

In Prokso code 407 means a wrong username or password or that the plan's traffic has run out. For 429, see the 429 error page.

Codes the Prokso gateway returns

With 407, check the credentials first, then the plan's balance in the dashboard. Purchased traffic does not expire, so after you buy more GB the same plan works again. Steps for each case are on the 407 error and 503 error pages.

How to tell a proxy code from a site code in curl -v

For https:// sites, curl first shows the response to CONNECT: this code always comes from the proxy. If it is not 200, the request ends there and never reaches the site. If the tunnel opened, the TLS lines follow, and the code after them was sent by the site.

For http:// sites there is no tunnel, and the proxy's answer and the site's answer arrive in the same place. Then the response text gives a hint: an error page of the proxy or a page of the site itself.

Codes that are often misread

Code 504 means that the proxy did not get a response from the site in time; it is not a login problem, and repeating the request often helps. The causes are listed on the 504 error page. Codes 301 and 302 are not errors: the site redirects to another address, and curl follows it only with the -L option.

Code 200 with an unexpected page, for example a check page instead of the content, means that the site answered but restricted access in its own way. The proxy is working fine in that case.