Java Http(s)URLConnection java.io.IOException：服务器返回 HTTP 响应代码：403

Question

java.io.IOException: Server returned HTTP response code: 403 for http://www.budgetbottle.com/vivino.xml

This URL is working (returns the contents) when running by Java class main method an at local tomcat server but it is throwing error when running on the tomcat server on production machine.

The code as follows:

URL url = new URL("http://www.budgetbottle.com/vivino.xml");    
HttpURLConnection urlcon = (HttpURLConnection) url.openConnection();
urlcon.addRequestProperty("User-Agent", "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36");
// System.setProperty("http.agent", "");
System.setProperty("http.agent", "Chrome");

// urlcons.setRequestProperty("Content-Language", "en-US");
// urlcons.setUseCaches(false);
// urlcons.setDoInput(true);
// urlcons.setDoOutput(true);

I have already applied the solutions provided on the similar questions asked on this forum but no solution works.

Update:
I just noticed, the wget utility also throws the same error at the production system while no issue at the local system. Please note the options like User-Agent are used

Does it a system specific error?

Answer 1

I used the code below and it worked fine for me. Do you have some kind of ratelimit or IP ban system on the server, that could be blocking your connection?

    URL url = new URL("http://www.budgetbottle.com/vivino.xml");
    HttpURLConnection urlcon = (HttpURLConnection) url.openConnection();
    urlcon.addRequestProperty("User-Agent", "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/63.0.3239.132 Safari/537.36");
    System.setProperty("http.agent", "Chrome");
    BufferedReader reader = new BufferedReader(new InputStreamReader(urlcon.getInputStream()));
    StringBuilder sb = new StringBuilder();
    String line = null;
    while ((line = reader.readLine()) != null)
    {
        sb.append(line + "\n");
    }
    System.out.println(sb.toString());

Answer 2

It is quite possible that the production server is running behind an Apache HTTPD server that is proxying the requests to a Tomcat Server. This kind of setup is favored in some deployments for the following reasons:

• It permits one to copy the staticly served elements of an application into the Apache HTTPD handling side, where Apache HTTPD is generally much faster than Tomcat in serving up static files from disk.
• It permits one to forward only "valid" requests, reducing the load on Tomcat.
• It permits one to not forward any request that might reconfigure the application deployments or configuration within Tomcat, even if someone accidentally deploys Tomcat's web management tools
• It permits one to use the web management tool provided the requests to do so come from a trusted set of internet addresses.

And there's a lot of additional items that might be of interest to a system admin, prompting them to deploy Tomcat behind Apache HTTPD.

In at least one scenario, it might also permit Apache HTTPD doing a challenge and response authentication in the HTTPD layer before forwarding the request to Tomcat.

You need to get a better understanding of your production deployment before you can proceed. Then you need to attempt to recreate it more accurately in your development environment.

Answer 3

Could it be that your production server has somehow restricted network connectivity (all http/https connection attempts redirected to a captive proxy returning 'access denied')?

Are you able to reach any other external site from your production environment?

Answer 4

exactly the same thing happened to me! How did you solve this issue?

Thanks.