From: Adam Thompson <arthompson1990@gmail.com>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] Displaying 401 responses
Date: Fri, 17 Apr 2015 19:03:36 +0100 [thread overview]
Message-ID: <20150417180336.GD5949@toaster.adamthompson.me.uk> (raw)
[-- 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 --]
next reply other threads:[~2015-04-17 18:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-17 18:03 Adam Thompson [this message]
2015-04-17 22:30 ` Karl Dahlke
2015-04-18 10:58 ` Adam Thompson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20150417180336.GD5949@toaster.adamthompson.me.uk \
--to=arthompson1990@gmail.com \
--cc=Edbrowse-dev@lists.the-brannons.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).