Welcome! Log In Create A New Profile


Status 401 Behaviour Issue

March 19, 2011 03:03PM
Hi all.

I noticed a certain behaviour of the 401 status code response I will like to change.

Firstly, in Apache, there is an html page for 401 that is defined in the error_page equivalent. When the request for a protected directory comes in, the user gets the form for the authentication and only if the authentication fails is that html page served.

With Nginx however, if I define an html page error_page for 401, this gets served every time a user requests the protected directory and there is no opportunity to fill in the authentication details.

Is it possible to set it up such that it behaves like Apache does? I.E. only return the html error_page if the authentication fails? This seems like a better implementation to me.

Running 0.8.54

Subject Author Posted

Status 401 Behaviour Issue

Dayo March 19, 2011 03:03PM

Re: Status 401 Behaviour Issue

unclepieman March 19, 2011 03:34PM

Re: Status 401 Behaviour Issue

Dayo March 19, 2011 03:57PM

Re: Status 401 Behaviour Issue

Francis Daly March 19, 2011 10:12PM

Re: Status 401 Behaviour Issue

Dayo March 20, 2011 12:20AM

Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 337
Record Number of Users: 8 on April 13, 2023
Record Number of Guests: 500 on July 15, 2024
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready