[Edbrowse-dev] Displaying 401 responses

[Edbrowse-dev] Displaying 401 responses

[Adam Thompson]

[-- Attachment #1: Type: text/plain, Size: 487 bytes --]

Hi all,

Just an announcement that I've just pushed a small change such that if you
abort authorisation we now continue the transfer.
This brings our behaviour more in line with the rfc as well as other browsers
and http clients.
This was prompted by a web app I use at work which sends 401 unauthorised but
then displays a log in form in the response body.
I've not fully tested this (i.e. ssl,
multiple auth methods) but in basic testing it appears to work as intended.

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

[Edbrowse-dev] Displaying 401 responses

[Karl Dahlke]

Thanks for this one.
I don't have any way to test it so I'll just go with the flow.
The diff makes perfect sense to me.

Karl Dahlke

Re: [Edbrowse-dev] Displaying 401 responses

[Adam Thompson]

[-- Attachment #1: Type: text/plain, Size: 530 bytes --]

On Fri, Apr 17, 2015 at 06:30:23PM -0400, Karl Dahlke wrote:
> Thanks for this one.
> I don't have any way to test it so I'll just go with the flow.
> The diff makes perfect sense to me.

We just need enough js support for the corresponding log in form to work and my
Windows usage will be more than halved.
It currently does odd things resulting in getting a json response and 2
download prompts... No idea what they're using behind the scenes there.

Cheers,
Adam.
PS: for testing I used the varius tools at http://httpbin.org/

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]