libmicrohttpd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Fwd: Re: [libmicrohttpd] [digest-auth]: responses to POST requests don't


From: Andreas Wehrmann
Subject: Fwd: Re: [libmicrohttpd] [digest-auth]: responses to POST requests don't get out
Date: Thu, 17 Feb 2011 16:46:39 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7

Sorry, I forgot this obvious information...
I'm using libmicrohttpd 0.9.7.
It's not the nonce thing, for which I provided the fix btw.

Best regards,
Andreas

-------- Original Message --------
Subject: Re: [libmicrohttpd] [digest-auth]: responses to POST requests don't get out
Date: Thu, 17 Feb 2011 15:43:52 +0100
From: Christian Grothoff <address@hidden>
Organization: Technische Universitaet Muenchen
To: address@hidden
CC: Andreas Wehrmann <address@hidden>


Dear Andreas,

First of all, which MHD version are you using?  There was a recent fix to nonce 
checking (see ChangeLog) which may help.  

To answer your concrete question, the actual transmission code is mostly in 
src/daemon/connection.c.

Happy hacking,

Christian

On Wednesday 16 February 2011 16:13:37 Andreas Wehrmann wrote:
> Hello!
> 
> I'm using digest authentication for delivering a small test page.
> For every connection (disregarding the request type) I check whether the
> source is authenticated as suggested by the tutorial.
> Delivery with authentication works fine.
> I added a page with a formular which issues a POST request when submitted.
> What I see in my application log when I submit the form is:
> 1. rx POST request
> 2. deny: new nonce needed
> 3. MHD_queue_auth_fail_response()
> 
> The client (Firefox 3.6.x) repeats the same request twice
> (the application flow is the same exactly).
> 
> So when the client sends the first POST request the server thinks it
> needs a new nonce,
> denies access and is supposed to send a proper response through calling
> MHD_queue_auth_fail_response().
> What are the other two POSTs for:
> 
> I noticed (using Wireshark) that the server doesn't respond to the POST
> requests,
> which would suggest that MHD_queue_auth_fail_response() failed
> (which according to its return code didn't).
> Unfortunately I don't have so much time at the moment so I was hoping to
> get a hint as to where I should look at to narrow the problem.
> The easiest thing would probably be to look at the part of code
> where the response is supposed to actually go out on the socket...
> where's that? :-)
> 
> Best regards,
> Andreas

reply via email to

[Prev in Thread] Current Thread [Next in Thread]