SSLClientVerify is always treated as required for a multiple locaiton config

Solution Verified - Updated -


  • We have multiple locations setup, one for a given context and the other for more specific content under that context. We want the main context location to be configured with SSL client cert verification and the more specific one without it, but the more specific location still acts as though SSLClientVerify is set to required.
<LocationMatch /foo/bar/image.jpg>
   SSLVerifyClient none

<Location /foo>
   SSLVerifyClient require
  • /foo/bar/image.jpg should be accessible without the client cert verification but this is not the case.


  • JBoss Enterprise Web Server (EWS)
  • JBoss Core Services (JBCS)
  • Apache httpd

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content