Re: [Jetty-support] Delay establishing a HTTPS connection with Firefox

View: New views
1 Messages — Rating Filter:   Alert me  

Parent Message unknown Re: [Jetty-support] Delay establishing a HTTPS connection with Firefox

by David Yu-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Matt,

these lists are deprecated, the ones at user@... are
the active user and dev lists.  I am cc'ing this to that list now..


Just to confirm, tomcat also uses sun's (nio) ssl engine yes?

Cheers,
dyu

Matt Doran wrote:

> Matt Doran wrote:
>> Hi guys,
>>
>> We use Jetty as the embedded web server in our product (PaperCut).  
>> In fact, we're one of the case studies on the web tide site here
>> <http://www.webtide.com/case_studies/>.  :)
>>
>> We've recently upgraded our application to use Java 6 and Jetty
>> 6.1.14 (from Jetty 5).   And we've found that establishing an HTTPS
>> connection to the server from Firefox 3 results in a 30 second delay
>> (which doesn't occur using other browsers).
>>
>> After enabling the JRE's SSL debug logging and googling the errors I
>> found, I came across your issue describing this problem (JETTY-567
>> <http://jira.codehaus.org/browse/JETTY-567>).  So the underlying
>> issue appears to be a bug in the Java SSL implementation.   And Greg
>> said that he'd raised the issue with Sun, but I couldn't find the
>> issue in the Sun Bug database.
>>
>> This is a pretty serious bug, and I'm surprised that there aren't
>> more people affected by this one!
>>
>> Does anyone have any news on this issue?  Or had any feedback from
>> Sun?  Does anyone know if this affects other web servers (like Tomcat)?
>>
>>
>>  
> fyi, I've just tried Tomcat on the same Java 6 VM, and it does not
> have the delay problem encountered in Jetty.
> However analysis of the Java SSL debug logs, shows that it has the
> same TLSv1 handshake failure, but it doesn't wait the 30 seconds
> before falling back to the SSLv3 connection.   I guess this is a
> difference in the implementations ... but maybe one of the Jetty
> developers can make sense of it and improve Jetty's behaviour in this
> case.
>
> I've attached the SSL logging of a Firefox connection to Jetty 6.1.14
> and Tomcat 6.0.18.   You can see the TLSv1 handshake failures in both
> ... but they react in different ways.  Jetty waits for more data from
> the client, and Tomcat fails with the "Unexpected end of handshake
> data" and moves on immediately.
>
> Regards,
> Matt
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------------
> This SF.net email is sponsored by:
> SourcForge Community
> SourceForge wants to tell your story.
> http://p.sf.net/sfu/sf-spreadtheword
> ------------------------------------------------------------------------
>
> _______________________________________________
> Jetty-support mailing list
> Jetty-support@...
> https://lists.sourceforge.net/lists/listinfo/jetty-support


------------------------------------------------------------------------------
This SF.net email is sponsored by:
SourcForge Community
SourceForge wants to tell your story.
http://p.sf.net/sfu/sf-spreadtheword
_______________________________________________
Jetty-support mailing list
Jetty-support@...
https://lists.sourceforge.net/lists/listinfo/jetty-support