[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: 307 status code handling in url-http-parse-headers
|
From: |
Nicolas Petton |
|
Subject: |
Re: 307 status code handling in url-http-parse-headers |
|
Date: |
Mon, 01 Feb 2016 18:42:31 +0100 |
|
User-agent: |
Notmuch/0.21 (http://notmuchmail.org) Emacs/25.1.50.3 (x86_64-unknown-linux-gnu) |
Yuri Khan <address@hidden> writes:
> The current version of HTTP/1.1 (RFC 7231) no longer requires
> confirmation on 301, 302 or 307. It documents that some clients MAY
> (but actually should not) change POST to GET on 301 and 302. It
> clarifies that clients MUST NOT change the method on a 307.
Thank you for the clarifications!
What should we do then? The current implementation seems to just
ignores the redirection, I would at least ask the user for a
confirmation.
Nico
--
Nicolas Petton
http://nicolas-petton.fr
signature.asc
Description: PGP signature
- 307 status code handling in url-http-parse-headers, Nicolas Petton, 2016/02/01
- Re: 307 status code handling in url-http-parse-headers, Alexis, 2016/02/01
- Re: 307 status code handling in url-http-parse-headers, Yuri Khan, 2016/02/01
- Re: 307 status code handling in url-http-parse-headers,
Nicolas Petton <=
- Re: 307 status code handling in url-http-parse-headers, Yuri Khan, 2016/02/01
- Re: 307 status code handling in url-http-parse-headers, Nicolas Petton, 2016/02/02
- Re: 307 status code handling in url-http-parse-headers, Lars Ingebrigtsen, 2016/02/02
- Re: 307 status code handling in url-http-parse-headers, Nicolas Petton, 2016/02/03
- Re: 307 status code handling in url-http-parse-headers, Lars Ingebrigtsen, 2016/02/03
- Re: 307 status code handling in url-http-parse-headers, Nicolas Petton, 2016/02/03
- Re: 307 status code handling in url-http-parse-headers, Nicolas Petton, 2016/02/04