Bug 47945 - SSLSessionCache directive mis-parses parens() in pathname
Summary: SSLSessionCache directive mis-parses parens() in pathname
Status: RESOLVED FIXED
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_ssl (show other bugs)
Version: 2.2.14
Hardware: All All
: P2 critical (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: FixedInTrunk
: 46420 48931 (view as bug list)
Depends on:
Blocks:
 
Reported: 2009-10-06 06:25 UTC by bugzilla33
Modified: 2014-10-23 01:22 UTC (History)
3 users (show)



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description bugzilla33 2009-10-06 06:25:07 UTC
[httpd-ssl.conf]
SSLSessionCache "shmcb:C:/Program Files (x86)/Apache Software Foundation/Apache2.2/logs/ssl_scache(512000)"

The error is:
SSLSessionCache: Invalid Argument: size has to be >- 8192 bytes

I THINK what is happening is that the parser is seeing the (x86) part of the file path and getting confused...
Comment 1 William A. Rowe Jr. 2009-10-06 09:18:09 UTC
Your analysis is correct (and description was wrong - it is an issue on any 
platform if the path includes parens).

The fix is to split the directive into a TAKE12, where if there is a second
argument, the paren parsing is disabled entirely.
Comment 2 Stefan Fritsch 2009-10-23 12:28:36 UTC
Fixed in trunk in r829185
Comment 3 Eric Covener 2010-03-17 20:14:32 UTC
*** Bug 48931 has been marked as a duplicate of this bug. ***
Comment 4 Christian Höltje 2010-07-15 12:29:03 UTC
Is this a dupe of Bug 46420?
Comment 5 Stefan Fritsch 2011-06-15 22:45:30 UTC
*** Bug 46420 has been marked as a duplicate of this bug. ***
Comment 6 Gili 2012-02-02 05:07:37 UTC
This bug was fixed over 2 years ago. Why hasn't it made it into an official release? I can still reproduce it in version 2.2.22.
Comment 7 bugzilla33 2012-02-02 09:43:09 UTC
one word sloppiness
Comment 8 Jeff Trawick 2014-10-22 15:37:58 UTC
This fixes the same issue with SSLStaplingCache.
Comment 9 Jeff Trawick 2014-10-23 01:22:18 UTC
The fix was in the initial 2.4.x release in early 2012.