-
1. Re: File Download over SSL
jonlee May 12, 2003 8:08 AM (in response to robgratz)Have you configured an SSL listener in server/instance/deploy/jbossweb-tomcat.sar/META-INF/jboss-service.xml where instance is the JBoss instance you are running - this is normally default? This will be bound to port 8443 normally. It is normally commented out. You will also need to create a certificate for it.
Note: if you are running the default JBoss instance, the file would be server/default/deploy/jbossweb-tomcat.sar/META-INF/jboss-service.xml in your JBoss distribution.
Refer to the Tomcat documents at the Tomcat site for creating a certificate for Tomcat.
For example, with the certificate file server/default/conf/tomcat.key, the SSL listener would look something like this:
<!-- Define a SSL Coyote HTTP/1.1 Connector on port 8443 -->
<Factory className="org.apache.coyote.tomcat4.CoyoteServerSocketFactory"
keystoreFile="${jboss.server.home.dir}/conf/tomcat.key"
clientAuth="false" protocol="TLS" /> -
2. Re: File Download over SSL
robgratz May 12, 2003 8:33 AM (in response to robgratz)I have the site running through SSL just fine. It's the file download that I'm having trouble with. All other pages are accessible from both SSL and non-SSL configurations. File download works fine in non-SSL mode but get the above mentioned error in SSL mode.
-
3. Re: File Download over SSL
jonlee May 12, 2003 10:19 AM (in response to robgratz)If the file is static content, can you download it via SSL? We've had no troubles with PDFs so just trying to get a feel for whether it is a mime-type definition, although it should work if it is working for the standard listener.
Are you doing any explicit context mapping? Again, just to get a feel for any other settings.
I doubt that JBoss is involved as the content delivery is managed by Tomcat.
Also, does anything show up in the Tomcat access logs or anything appear in the server logs? -
4. Re: File Download over SSL
robgratz May 12, 2003 12:19 PM (in response to robgratz)The problem ended up being an IE problem.
http://support.microsoft.com/?kbid=323308
By replacing the "no-cache" header directives with "no-store", everything worked fine.
Thanks for the responses.