Re: Turning cookie JSESSIONID off (selectively)
Ryszard, Do you need cookies, or do you just need session management? You can get the latter by using URL rewriting. Basically, you just need to pass every URL written to your pages (including form action attribute values) through response.encodeURL(String URL) before writing to the page. If you do this, you should then be able to turn off cookies (some server parameter, at least in Tomcat 5, although I don't recall where) and still maintain session. Jeff Jackson On Fri, 24 Oct 2003, Ryszard Lach wrote: Hi. Is there possible to turn off cookie JSESSIONID? I would like to use squid in reverse-proxy mode with a Java application (Tomcat 4.1), but squid does not cache pages with this cookie set. I can not turn it off at all, because a part o my application uses cookies for session management. Any suggestions will be appreciated. Richard. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Content length
Can the client handle chunked encoding? Then you don't need to set content-length at all. Jeff Jackson On Fri, 24 Oct 2003, William Bondy wrote: I have a client browser that acts a bit in a non-standard fashion, for http responses with content-length set (keep-alive) it expects the content-length worth of data PLUS an extra \r\n that is not counted in the content length header sent. When I set the HttpServletResponse contentLength header to value X and then write X+2 bytes to the stream, only X bytes get written. I assume the the underlying control is only sending what the header is set to. Is there anyway to get around this, ie. set the content length header to X and X+2 bytes? Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mozilla, SSL certificates, and Tomcat 5
What version of Mozilla are you running, and on what system? Turns out that Mozilla 1.2.1 on my Linux box is able to use SSL. It also does form-based authentication without any trouble. Jeff Adam Hardy wrote: Jeff, I get strange behaviour with Moz tomcat5 SSL but not what you're describing. To do with the form-based authentication. Adam On 10/22/2003 05:58 PM Jeff Jackson wrote: I'm using Sun's j2sdk1.4.2. Are you saying that using IBM's JVM would make a difference? I've read the howto. Again, I have SSL working with IE6. Mozilla 1.4 on the same machine gets a server certificate, but then fails to get any data. Seems like a handshake problem to me. Bill Barker wrote: Are you using IBM's JVM? If so, please see the latest SSL-howto documentation for how to get SSL working. Jeff Jackson [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Short version: I can access Tomcat via SSL from IE6, but not from Mozilla 1.4/Netscape 7.1. Is this a known problem, and if so, what's the work-around? Long version: I've installed Sun's Java Web Services Developer Pack 1.3 version of Tomcat 5 under Linux. I also created a self-signed certificate using the Java keytool, accepting the default keystore location and using the default changeit password. When I enable SSL (either by removing comment delimiters from the SSL Connector in the out-of-the-box server.xml, or by running the web-based admin tool) and restart Tomcat, there are no error messages in any log files. And I can access the SSL port with an https URL using IE6 from a Windows client. But Mozilla 1.4 and Netscape 7.1 (on the same Windows client I used for IE) both give a The document contains no data. alert when I try to access the same URL, after a several second delay and a number of Connecting/Connected status messages. These browsers have had no trouble accessing other https URL's, so I'm assuming that it's a Tomcat issue. I have tried changing the server.xml Host name from localhost to my actual host name and changing the Factory protocol from TLS to SSL (based on something I saw in another SSL question). This had no apparent effect. I also tried using a trial Verisign-signed certificate, with the same results: IE6 can access the site, Mozilla cannot. What am I missing? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mozilla, SSL certificates, and Tomcat 5
I'm using Sun's j2sdk1.4.2. Are you saying that using IBM's JVM would make a difference? I've read the howto. Again, I have SSL working with IE6. Mozilla 1.4 on the same machine gets a server certificate, but then fails to get any data. Seems like a handshake problem to me. Bill Barker wrote: Are you using IBM's JVM? If so, please see the latest SSL-howto documentation for how to get SSL working. Jeff Jackson [EMAIL PROTECTED] wrote in message news:[EMAIL PROTECTED] Short version: I can access Tomcat via SSL from IE6, but not from Mozilla 1.4/Netscape 7.1. Is this a known problem, and if so, what's the work-around? Long version: I've installed Sun's Java Web Services Developer Pack 1.3 version of Tomcat 5 under Linux. I also created a self-signed certificate using the Java keytool, accepting the default keystore location and using the default changeit password. When I enable SSL (either by removing comment delimiters from the SSL Connector in the out-of-the-box server.xml, or by running the web-based admin tool) and restart Tomcat, there are no error messages in any log files. And I can access the SSL port with an https URL using IE6 from a Windows client. But Mozilla 1.4 and Netscape 7.1 (on the same Windows client I used for IE) both give a The document contains no data. alert when I try to access the same URL, after a several second delay and a number of Connecting/Connected status messages. These browsers have had no trouble accessing other https URL's, so I'm assuming that it's a Tomcat issue. I have tried changing the server.xml Host name from localhost to my actual host name and changing the Factory protocol from TLS to SSL (based on something I saw in another SSL question). This had no apparent effect. I also tried using a trial Verisign-signed certificate, with the same results: IE6 can access the site, Mozilla cannot. What am I missing? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Mozilla, SSL certificates, and Tomcat 5
Short version: I can access Tomcat via SSL from IE6, but not from Mozilla 1.4/Netscape 7.1. Is this a known problem, and if so, what's the work-around? Long version: I've installed Sun's Java Web Services Developer Pack 1.3 version of Tomcat 5 under Linux. I also created a self-signed certificate using the Java keytool, accepting the default keystore location and using the default changeit password. When I enable SSL (either by removing comment delimiters from the SSL Connector in the out-of-the-box server.xml, or by running the web-based admin tool) and restart Tomcat, there are no error messages in any log files. And I can access the SSL port with an https URL using IE6 from a Windows client. But Mozilla 1.4 and Netscape 7.1 (on the same Windows client I used for IE) both give a The document contains no data. alert when I try to access the same URL, after a several second delay and a number of Connecting/Connected status messages. These browsers have had no trouble accessing other https URL's, so I'm assuming that it's a Tomcat issue. I have tried changing the server.xml Host name from localhost to my actual host name and changing the Factory protocol from TLS to SSL (based on something I saw in another SSL question). This had no apparent effect. I also tried using a trial Verisign-signed certificate, with the same results: IE6 can access the site, Mozilla cannot. What am I missing? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
