Re: AW: AW: WebSockets and HTTPS problems
On 10/10/2012 19:57, Mark Thomas wrote: On 10/10/2012 19:51, Steffen Heil (Mailinglisten) wrote: Hi I just took a look at this. The examples work out of the box for HTTPS with BIO but not with NIO. This looks like a Tomcat bug at this point. I'll take a look. What would I need to do to switch to BIO for now? Change the protocol attribute for your connector. See the docs. And does Comet work with BIO? No, but APR does. ( I haven't tested APR, HTTPS and WebSocket yet). If you can hang on for a few hours, I might have a fix for you. See if this fixes if for you: http://people.apache.org/~markt/dev/tomcat-7/v7.0.33-r1397089/apache-tomcat-7.0.33-r1397089.tar.gz This is not an official release. Use it at your own risk. I'll take it down again in a few days. Any feedback appreciated. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: AW: AW: WebSockets and HTTPS problems
2012/10/11 Mark Thomas ma...@apache.org: On 10/10/2012 19:57, Mark Thomas wrote: On 10/10/2012 19:51, Steffen Heil (Mailinglisten) wrote: Hi I just took a look at this. The examples work out of the box for HTTPS with BIO but not with NIO. This looks like a Tomcat bug at this point. I'll take a look. What would I need to do to switch to BIO for now? Change the protocol attribute for your connector. See the docs. And does Comet work with BIO? No, but APR does. ( I haven't tested APR, HTTPS and WebSocket yet). If you can hang on for a few hours, I might have a fix for you. See if this fixes if for you: http://people.apache.org/~markt/dev/tomcat-7/v7.0.33-r1397089/apache-tomcat-7.0.33-r1397089.tar.gz This is not an official release. Use it at your own risk. I'll take it down again in a few days. Mark, I see you committed the fix to trunk in http://svn.apache.org/viewvc?view=revisionrevision=1397086 but I do not see such commit for 7.0.x (only a changelog update in r1397089). What am I missing? Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
AW: AW: AW: WebSockets and HTTPS problems
Hi See if this fixes if for you: http://people.apache.org/~markt/dev/tomcat-7/v7.0.33-r1397089/apache- tomcat-7.0.33-r1397089.tar.gz Preliminary tests look promising. Everything worked (using a few single click tests so far). Thanks! This is not an official release. Use it at your own risk. Understood. Is there any reason to expect this version to be in any way worse than 7.0.32? Is there any estimation, when a new release might happen? (No urge, just asking) I'll take it down again in a few days. As for me, you may already do so. Any feedback appreciated. Again, so far everything worked. We will test it a lot more in the next days and I will report back. Thanks again, Steffen smime.p7s Description: S/MIME cryptographic signature
Re: AW: AW: AW: WebSockets and HTTPS problems
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steffen, On 10/11/12 11:36 AM, Steffen Heil (Mailinglisten) wrote: See if this fixes if for you: http://people.apache.org/~markt/dev/tomcat-7/v7.0.33-r1397089/apache- tomcat-7.0.33-r1397089.tar.gz Preliminary tests look promising. Everything worked (using a few single click tests so far). Thanks! This is not an official release. Use it at your own risk. Understood. Is there any reason to expect this version to be in any way worse than 7.0.32? Is there any estimation, when a new release might happen? (No urge, just asking) Tomcat 7.0.x releases have been roughly once per month, and we just had one this week. It's reasonable to expect at least one more before the end of the year and perhaps two. - -chris -BEGIN PGP SIGNATURE- Version: GnuPG/MacGPG2 v2.0.17 (Darwin) Comment: GPGTools - http://gpgtools.org Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlB28qoACgkQ9CaO5/Lv0PDxbwCgwSs5SjM3Da9vgCRKuA9SDPE7 S3kAniSDm/l/oHEe8CYAcm7xVtZTcCoi =T53X -END PGP SIGNATURE- - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: AW: AW: WebSockets and HTTPS problems
Konstantin Kolinko knst.koli...@gmail.com wrote: 2012/10/11 Mark Thomas ma...@apache.org: On 10/10/2012 19:57, Mark Thomas wrote: On 10/10/2012 19:51, Steffen Heil (Mailinglisten) wrote: Hi I just took a look at this. The examples work out of the box for HTTPS with BIO but not with NIO. This looks like a Tomcat bug at this point. I'll take a look. What would I need to do to switch to BIO for now? Change the protocol attribute for your connector. See the docs. And does Comet work with BIO? No, but APR does. ( I haven't tested APR, HTTPS and WebSocket yet). If you can hang on for a few hours, I might have a fix for you. See if this fixes if for you: http://people.apache.org/~markt/dev/tomcat-7/v7.0.33-r1397089/apache-tomcat-7.0.33-r1397089.tar.gz This is not an official release. Use it at your own risk. I'll take it down again in a few days. Mark, I see you committed the fix to trunk in http://svn.apache.org/viewvc?view=revisionrevision=1397086 but I do not see such commit for 7.0.x (only a changelog update in r1397089). What am I missing? Probably that I did the merge but forgot the commit. Ill check when I turn my desktop back on. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
AW: WebSockets and HTTPS problems
Hi Check to see if the WebSocket examples that ship with Tomcat work with your configuration. If they don't compare the differences between the default configuration and you configuration to and find the change that breaks stuff. First, thanks for the reply. I downloaded tomcat 7.0.32 again and replaced the connectors in the configuration with my own (minus the executor references). Nothing else was changed. The WebSocket chat example works with http on port 80, but not on port 8443. It says: Info: WebSocket connection opened. * Guest3 has joined. And as soon as I send something: Info: WebSocket closed. The message does not get back to the client. So the problem must in my connector configuration: Connector port=80 protocol=org.apache.coyote.http11.Http11NioProtocol connectionTimeout=2 redirectPort=443 / Connector port=8443 protocol=org.apache.coyote.http11.Http11NioProtocol SSLEnabled=true scheme=https secure=true clientAuth=false sslProtocol=TLS connectionTimeout=2 keystoreFile=../https.p12 keystorePass=XXX keystoreType=PKCS12 URIEncoding=UTF-8 / I don't see it; how can this happen? What can I do to debug this any further? Best regards, Steffen smime.p7s Description: S/MIME cryptographic signature
Re: AW: WebSockets and HTTPS problems
On 10/10/2012 17:41, Steffen Heil (Mailinglisten) wrote: Hi Check to see if the WebSocket examples that ship with Tomcat work with your configuration. If they don't compare the differences between the default configuration and you configuration to and find the change that breaks stuff. First, thanks for the reply. I downloaded tomcat 7.0.32 again and replaced the connectors in the configuration with my own (minus the executor references). Nothing else was changed. The WebSocket chat example works with http on port 80, but not on port 8443. It says: Info: WebSocket connection opened. * Guest3 has joined. And as soon as I send something: Info: WebSocket closed. The message does not get back to the client. So the problem must in my connector configuration: I just took a look at this. The examples work out of the box for HTTPS with BIO but not with NIO. This looks like a Tomcat bug at this point. I'll take a look. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
AW: AW: WebSockets and HTTPS problems
Hi I just took a look at this. The examples work out of the box for HTTPS with BIO but not with NIO. This looks like a Tomcat bug at this point. I'll take a look. What would I need to do to switch to BIO for now? And does Comet work with BIO? Regards, Steffen smime.p7s Description: S/MIME cryptographic signature
Re: AW: AW: WebSockets and HTTPS problems
On 10/10/2012 19:51, Steffen Heil (Mailinglisten) wrote: Hi I just took a look at this. The examples work out of the box for HTTPS with BIO but not with NIO. This looks like a Tomcat bug at this point. I'll take a look. What would I need to do to switch to BIO for now? Change the protocol attribute for your connector. See the docs. And does Comet work with BIO? No, but APR does. ( I haven't tested APR, HTTPS and WebSocket yet). If you can hang on for a few hours, I might have a fix for you. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
