@sensewolf said in Can't protect certain path only with client certificate:
-- The expected outcome is that in order to access the specific path, a client certificate is required. Surprisingly, however, the path becomes publicly accessible again without the client certificate --
I don't understand why this doesn't work. The setup is basically the same as for my other accessible and protected domains with the only difference that in this case only a certain path should be protected.
Did you put this rule to the top, so that it is probed and executed before the other one?
For testing the ACLs just use a simple rule, which give a clear result like "http request deny".
Why isn't this working? What am I missing?
Maybe someone will see it if you post the whole configuration.