all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Alexis <flexibeast@gmail.com>
To: Nicolas Petton <nicolas@petton.fr>
Cc: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: Re: 307 status code handling in url-http-parse-headers
Date: Tue, 02 Feb 2016 01:54:30 +1100	[thread overview]
Message-ID: <87oac0wkex.fsf@gmail.com> (raw)
In-Reply-To: <87oac0o64s.fsf@petton.fr>


Nicolas Petton <nicolas@petton.fr> writes:

> I see that `url-http-parse-headers' won't redirect a 307 
> response for a POST request.
>
> There's a comment about 301/302 status codes, which says that 
> for other requests than HEAD and GET, the user agent must not 
> automatically redirect, which seems to follow the RFC.
>
> However, should we ask the user confirmation for the redirection 
> and do the redirect depending on the user's choice?

Sorry, do you mean, ask the user for redirect confirmation in the 
context of HEAD and GET requests? The reason i ask is this:

https://debbugs.gnu.org/cgi/bugreport.cgi?bug=18290

Unfortunately i've not yet been able to find the time to try to 
work on this issue, but asking users for confirmation in the 
context of a PROPFIND request seems like it might not be a good 
idea ....


Alexis.



  reply	other threads:[~2016-02-01 14:54 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 [this message]
2016-02-01 15:01   ` Nicolas Petton
2016-02-01 17:01 ` Yuri Khan
2016-02-01 17:42   ` Nicolas Petton
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=87oac0wkex.fsf@gmail.com \
    --to=flexibeast@gmail.com \
    --cc=emacs-devel@gnu.org \
    --cc=monnier@iro.umontreal.ca \
    --cc=nicolas@petton.fr \
    /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.