1

We've configured Apache HTTPd to use

  • Basic Authentication
  • Serve a custom error document

Now, the user gets different results, when canceling the authentication in the first step or after submitting wrong credentials.

Example

The user calls the following URL: "example.com/pageXYZ

Expected behavior

  1. Browser shows authentication window
  2. User cancels the authentication
  3. Correct ErrorDocument is shown (Additional login mask with redirect to pageXYZ)

Wrong(?) behavior

  1. Browser shows authentication window
  2. User submits wrong credentials
  3. Browser shows authentication window again
  4. User cancels the authentication
  5. Correct ErrorDocument is shown, but without redirect to pageXYZ

Does anyone know this behaviour or can tell, why it is like it is and if it is possible to get the expected behavior in both scenarios.

3
  • Is there any relevantinformation in your access / error logs?
    – user9517
    Jan 27, 2014 at 6:56
  • @lain No nothing. Logs are good so far. But good hint, I will try to setup a finer logging...
    – Adrian
    Jan 27, 2014 at 6:57
  • From the logs I can say, that the referrer isn't send to the ErrorDocument "handler" on the second authorization request.
    – Adrian
    Jan 27, 2014 at 7:12

1 Answer 1

0

Okay, just found out, that the problem is within the underlying application and not the Apache HTTPd.

On the first request to deliver the ErrorDocument it does some processing, which isn't done on subsequent requests.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .