Welcome! Log In Create A New Profile

Advanced

Re: 100-continue and 401

Luka Perkov
March 20, 2013 04:40AM
Hi Vladimir,

On Tue, Mar 19, 2013 at 07:36:07PM +0400, Vladimir Shebordaev wrote:
> Both requests do look basically correct just like the nginx's and
> curl's behavior. You didn't supply any credentials for
> authentication to continue.

I know I didn't. That is the example test, if my SCGI daemon gets
request without username and password it will reply to nginx with this:

Status: 401 Unauthorized
WWW-Authenticate: Basic realm="bla-bla-bla"

Then nginx will pass that to the client. The problem is that nginx sends
"100 Continue" first. I think that my SCGI code is correct, I'm not sure
if nginx should send "100 Continue" before "401 Unauthorized".

My guess is that the same will happen using CGI, FastCGI, uWSGI or when
using any upstream server. Somebody correct me if I'm wrong.

Luka

_______________________________________________
nginx-devel mailing list
nginx-devel@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx-devel
Subject Author Views Posted

100-continue and 401

Luka Perkov 4230 March 19, 2013 08:28AM

Re: 100-continue and 401

Vladimir Shebordaev 1964 March 19, 2013 11:38AM

Re: 100-continue and 401

Luka Perkov 1181 March 20, 2013 04:40AM

Re: 100-continue and 401

Dmitry Petrov 1415 March 20, 2013 05:14AM

Re: 100-continue and 401

Nick Kew 1390 March 19, 2013 01:12PM

Re: 100-continue and 401

Luka Perkov 1181 March 20, 2013 05:12AM



Sorry, you do not have permission to post/reply in this forum.

Online Users

Guests: 212
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