Hi Luka,
There was a post about similar problem on nginx forum with reply from Igor:
http://forum.nginx.org/read.php?2,212533,212549#msg-212549
On Wed, Mar 20, 2013 at 12:44 PM, Luka Perkov wrote:
> Hi Vladimir,
>
> On Tue, Mar 19, 2013 at 07:36:07PM +0400, Vladimir Shebordaev wrote:
> > Both r
Hi Nick,
On Tue, Mar 19, 2013 at 05:09:38PM +, Nick Kew wrote:
> On 19 Mar 2013, at 12:31, Luka Perkov wrote:
> > I'm using nginx as a frontend for my SCGI application and I want to
> > $ curl -v -X POST -d "@/path/to/some/blob" http://127.0.0.1:8000/
> > * About to connect() to 127.0.0.1 port
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
On 19 Mar 2013, at 12:31, Luka Perkov wrote:
> Hi all,
>
> I'm using nginx as a frontend for my SCGI application and I want to
> handle authentication in my SCGI code. I have to deal with POST
> requests. Is it ok that nginx sends "401 Unauthorized" after sending
> "100 Continue"?
>
> Are both
Hi,
On 19.03.2013 16:31, Luka Perkov wrote:
Hi all,
I'm using nginx as a frontend for my SCGI application and I want to
handle authentication in my SCGI code. I have to deal with POST
requests. Is it ok that nginx sends "401 Unauthorized" after sending
"100 Continue"?
Are both requests bellow
Hi all,
I'm using nginx as a frontend for my SCGI application and I want to
handle authentication in my SCGI code. I have to deal with POST
requests. Is it ok that nginx sends "401 Unauthorized" after sending
"100 Continue"?
Are both requests bellow correct?
I'm asking because of this curl messa
