|Summary:||Need directive to control use and timeout of session ticket|
|Product:||Apache httpd-2||Reporter:||matty <matty.roland1>|
|Component:||mod_ssl||Assignee:||Apache HTTPD Bugs Mailing List <bugs>|
Description matty 2011-03-04 06:11:16 UTC
FireFox 3.6 supports session cache as a ticket based on RFC5077. When FireFox 3.6 contacts Apache 2.2.15, SSLSessionCacheTimeout does not work even if NoSessionIdContext option in SSLOptions directive is set. In this case, the timeout is always 300 seconds and renegotiation happens after that. We want Apache to be able to control the use and timeout of the ticket used as the session cache. We want: 1. Want to control the timeout of the session even if tickets of RFC4507/RFC5077 are used. 2. Want to have a directive to disable using ticket at Apache side This is "SSLSessionTicketExtension" in the discussion at following thread: http://email@example.com/msg46133.html
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:06 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd. As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd. If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question. If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with. Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.