https://bz.apache.org/bugzilla/show_bug.cgi?id=62232
--- Comment #20 from Yann Ylavic <[email protected]> --- > I don't see the word SSLProxyEnable anywhere on this page: Yes my bad, I meant SSLProxyEngine. > Is this a new requirement (SSLProxyEngine)? > I mean is it new to require it in the VirtualHost context? We do already > include it in the server config context. What I meant is that the bug would not trigger if some SSLProxy* directive (for instance SSLProxyEngine) is in each context (<FilesMatch>, <Location> in your case) where another SSL* directive (for instance SSLRequire) is used. But this is obviously not a new requirement, clearly a bug in the new merge process which I tried (badly) to explain... -- 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]
