You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When is directive SSLVerifyClient require used inside of configuration section Location/Directory it seems like gridsite won't do anything with the request and I'll get an error from ssl module saying: Certificate Verification: Error (40): proxy certificates not allowed, please set the appropriate flag.
I need the setup where some locations are authorized with gridsite and some are not so I can't use the directive globaly.
I fail to see a feasible way to get this configuration working. When you change the SSLVerifyClient directive, the mod_ssl triggers re-negotiation of the TLS connection and uses its own verification routine, which can't be overridden by Gridsite as in case when usual connection is being handled.
What could work is the the other way round, ie. specifying SSLVerifyClient Require on the Server level and using SSLVerifyClient None on Locations/Direstories where no client authentication is requested. (I haven't tried though).
When is directive
SSLVerifyClient require
used inside of configuration sectionLocation
/Directory
it seems like gridsite won't do anything with the request and I'll get an error from ssl module saying:Certificate Verification: Error (40): proxy certificates not allowed, please set the appropriate flag
.I need the setup where some locations are authorized with gridsite and some are not so I can't use the directive globaly.
I attach apache configurations and logs (of one request) - both working and not working.
apache-conf-bad.txt
apache-conf-good.txt
apache-log-bad.txt
apache-log-good.txt
The text was updated successfully, but these errors were encountered: