Topic: 401's in acess log after authentication with mod_authnz_sspi

[Brian]

I haven't worked with Apache HTTPD for a very long time. How long? Last time I deployed Apache was in the 2.0 days. I recently deployed the 2.4 binaries from AL, added to that from another source mod_authnz_sspi with success.

The HTTPD server has no vhosts, it is only fronting for Tomcat through the jk_module. So authentication for the apps that require it goes through SSPI which is set to require members of a speicfic domain security group. Again, this all works - access is granted with succesful authentication.

The strange thing is in the access.log, with each hit to the resource (e.g. /Location or /Directory) I see a two or more 401's followed by the normal 200, 302 and 304 status codes. When I saw the 401's I thoguht that was wierd because post-authentication access is unincumbered.

Any one have thoughts as to why after successful authentication I'd be seeing 401's?

Here are a couple of snippets from the access log showing the results:

I've been prompted for NT credentials, I enter them and am able to proceed. I see 401's though after authentcation has occured:

[James Blond]

That modules has a lot of issues with 2.4 version of apache. Might try the successor https://github.com/YvesR/mod_authn_ntlm