all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Nicolas Petton <nicolas@petton.fr>
To: Yuri Khan <yuri.v.khan@gmail.com>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: 307 status code handling in url-http-parse-headers
Date: Mon, 01 Feb 2016 18:42:31 +0100	[thread overview]
Message-ID: <87egcwnx88.fsf@petton.fr> (raw)
In-Reply-To: <CAP_d_8W5YHnukJRZ2tqLL8Z0W_1K8+3qse9Rnp26QwinmvUrGg@mail.gmail.com>

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

Yuri Khan <yuri.v.khan@gmail.com> 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

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 512 bytes --]

  reply	other threads:[~2016-02-01 17:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-01 14:30 307 status code handling in url-http-parse-headers Nicolas Petton
2016-02-01 14:54 ` Alexis
2016-02-01 15:01   ` Nicolas Petton
2016-02-01 17:01 ` Yuri Khan
2016-02-01 17:42   ` Nicolas Petton [this message]
2016-02-01 18:08     ` Yuri Khan
2016-02-02 22:28       ` Nicolas Petton
2016-02-03  0:27         ` Lars Ingebrigtsen
2016-02-03  8:49           ` Nicolas Petton
2016-02-03  9:24             ` Lars Ingebrigtsen
2016-02-03 10:27               ` Nicolas Petton
2016-02-04 17:00               ` Nicolas Petton

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=87egcwnx88.fsf@petton.fr \
    --to=nicolas@petton.fr \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=yuri.v.khan@gmail.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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.