WebLogic 6.0 HttpURLConnection class won't let me connect to a proxy

Question

          I am getting a '400' error (which means the server cannot understand
          the request, I believe) when I attempt to connect to a proxy server
          to download the auto-configuration (.pac) file - don't ask why,
          it's a long story.
          My code works fine when I run it outside WebLogic from a vanilla
          Java class (using Sun's standard URLConnection class), but as soon
          as I put it inside a servlet in WebLogic 6.0, and it's wrapped
          by the weblogic.net.http.HttpURLConnection class, I get the following
          stack trace:
          java.io.FileNotFoundException: Response: '400' for url: 'http://corporate-proxy-server-name:8080'
          at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:351)
          at com.csfb.gws.proxy.ProxyFinder.getProxyString(ProxyFinder.java:82)
          at com.csfb.gws.proxy.ProxyFinder.getProxiesForIpAddress(ProxyFinder.java:46)
          at com.csfb.gws.proxy.test.TestProxyFinderServlet.doPost(TestProxyFinderServlet.java:52)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:208)
          at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1127)
          at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1529)
          at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          Does anyone have any idea why this is happening? It certainly seems
          as though the WebLogic wrapper class is not working the same as
          Sun's standard HttpURLConnection.
          Any advice would be greatly appreciated.
          Cheers
          Dave
          

Answer 1

You can use something like this:
          URLStreamHandler handler = new sun.net.www.protocol.http.Handler();
          URL url = new URL(null, "http://yourserver", handler);
          to use Sun's handler instead of WebLogic's. (you will have to edit weblogic.policy
          accordingly to allow your code to specify handler).
          Dave Blumenfeld <[email protected]> wrote:
          > WebLogic Server automatically wraps its own HttpURLConnection class
          > around the Sun one. I haven't explicitly requested that it do so.
          > Don't know if I have any control over that.
          > "Xiang Rao" <[email protected]> wrote:
          >>
          >>Why not just use Sun's HttpURLConnection if it works fine
          >>for you?
          >>The only thing you need to do is adding java.net to any
          >>related
          >>variable declaration such as java.net.HttpURLConnection
          >>= (java.net.HttpURLConnection)url.openConnection().
          >>
          >>
          >>
          >>"Dave Blumenfeld" <[email protected]> wrote:
          >>>
          >>>I am getting a '400' error (which means the server cannot
          >>>understand
          >>>the request, I believe) when I attempt to connect to
          >>a
          >>>proxy server
          >>>to download the auto-configuration (.pac) file - don't
          >>>ask why,
          >>>it's a long story.
          >>>
          >>>My code works fine when I run it outside WebLogic from
          >>>a vanilla
          >>>Java class (using Sun's standard URLConnection class),
          >>>but as soon
          >>>as I put it inside a servlet in WebLogic 6.0, and it's
          >>>wrapped
          >>>by the weblogic.net.http.HttpURLConnection class, I get
          >>>the following
          >>>stack trace:
          >>>
          >>>java.io.FileNotFoundException: Response: '400' for url:
          >>>'http://corporate-proxy-server-name:8080'
          >>>
          >>> at weblogic.net.http.HttpURLConnection.getInputStream(HttpURLConnection.java:351)
          >>>
          >>> at com.csfb.gws.proxy.ProxyFinder.getProxyString(ProxyFinder.java:82)
          >>>
          >>> at com.csfb.gws.proxy.ProxyFinder.getProxiesForIpAddress(ProxyFinder.java:46)
          >>>
          >>> at com.csfb.gws.proxy.test.TestProxyFinderServlet.doPost(TestProxyFinderServlet.java:52)
          >>>
          >>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:760)
          >>>
          >>> at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
          >>>
          >>> at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubImpl.java:208)
          >>>
          >>> at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppServletContext.java:1127)
          >>>
          >>> at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestImpl.java:1529)
          >>>
          >>> at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:137)
          >>>
          >>> at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:120)
          >>>
          >>>
          >>>Does anyone have any idea why this is happening? It certainly
          >>>seems
          >>>as though the WebLogic wrapper class is not working the
          >>>same as
          >>>Sun's standard HttpURLConnection.
          >>>
          >>>Any advice would be greatly appreciated.
          >>>Cheers
          >>>Dave
          >>
          Dimitri