2011年3月19日星期六

Re: Status 401 Behaviour Issue

Do u mean a 403?

On 3/19/11, Dayo <nginx-forum@nginx.us> wrote:
> 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
>
> Thanks
>
> Posted at Nginx Forum:
> http://forum.nginx.org/read.php?2,184007,184007#msg-184007
>
>
> _______________________________________________
> nginx mailing list
> nginx@nginx.org
> http://nginx.org/mailman/listinfo/nginx
>

--
Sent from my mobile device

Payam Tarverdyan Chychi
Network Security Specialist / Network Engineer

_______________________________________________
nginx mailing list
nginx@nginx.org
http://nginx.org/mailman/listinfo/nginx

没有评论:

发表评论