https://issues.apache.org/bugzilla/show_bug.cgi?id=42929
[email protected] changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|INVALID |WONTFIX --- Comment #7 from [email protected] 2009-11-16 15:33:51 UTC --- This is a ridiculous resolution. Jim's comment agrees that the behavior of the web server under these conditions is "not expected to be stable or consistant[sic]" yet marks the bug as "RESOLVED INVALID" despite the following facts: 1) Many production web servers do in fact make use of this type of configuration (especially in shared hosting scenarios). 2) Apache offers no warning nor error when this type of configuration is implemented (despite the fact that detecting this situation is trivial). 3) With Server Name Identification, it is perfectly possible to correctly map SSL requests to a name-based virtual host 4) The bug is 100% reproducible and absolutely accurately reported (it is quite stable and consistent--just wrong) Resolve it as won't fix-- that's what you're really saying... or mark it as low priority and give someone like the Freek the opportunity to contribute a patch... or fix it by causing apache to warn under these conditions, something like "Warning: Use of SSL and Named VHOSTS is undocumented and is not expected to be stable or consistent" or something like that and resolve it as fixed... But don't call INVALID something that is 100% reproducible as obviously incorrect behavior. Either there's a bug in apache's handling of SSL for named VHOSTs or there's a bug in apache's config processing that allows for SSL in named VHOSTS. Which is the real bug is left as an exercise for the reader. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
