How to use Sun's HttpsURLConnection in 6.0

Question

          I have a servlet, which opens a connection to a https site. I
          was able to solve this problem in version 5.1 by adding the
          following in weblogic.policy
          permission
          javva.security.AllPermission "java.protocol.handler.pkgs", "read"
          ;, and setting weblogic.security.ssl.enable=false in the
          properties file. I tried the same in version 6.0, but it doesn't
          seem to work.
          Does anyone have any suggestions?
          Thanks.
          

Answer 1

From example:
          test.jsp:
          <%@ page import="java.io.*" %>
          <%@ page import="java.net.*" %>
          <%
          java.security.Security.addProvider(new com.sun.net.ssl.internal.ssl.Provider());
          URL etrade = new URL(null,
          "https://trading.etrade.com/cgi-bin/gx.cgi/AppLogic+Loginpage",
          new com.sun.net.ssl.internal.www.protocol.https.Handler());
          BufferedReader br = new BufferedReader(new InputStreamReader(etrade.openStream()));
          String line;
          while((line = br.readLine()) != null) {
          out.println(line);
          br.close();
          %>
          Mike G <[email protected]> wrote:
          > Would you mind sending me an example.
          > When you mean security permissions, do you mean setting the SSL
          > HandlerEnabled property to false, and adding permission
          > java.security.AllPermission "java.protocol.handler.pkgs", "read";
          > to the weblogic.policy file?
          > Thanks for your help.
          > Dimitri Rakitine <[email protected]> wrote:
          >>I use the URL(URL context, String spec, URLStreamHandler handler) constuctor
          >>and use sun's streamhandler - this doesn't require any configuration changes
          >>(except security permissions).
          >>
          >>Mike G <[email protected]> wrote:
          >>
          >>> I have a servlet, which opens a connection to a https site. I
          >>> was able to solve this problem in version 5.1 by adding the
          >>> following in weblogic.policy
          >>> permission
          >>> javva.security.AllPermission "java.protocol.handler.pkgs", "read"
          >>> ;, and setting weblogic.security.ssl.enable=false in the
          >>> properties file. I tried the same in version 6.0, but it doesn't
          >>> seem to work.
          >>
          >>> Does anyone have any suggestions?
          >>> Thanks.
          >>
          >>Dimitri
          Dimitri