From: Lars Ingebrigtsen <larsi@gnus.org>
To: Shiyao Ma <i@introo.me>
Cc: Nicolas Petton <nicolas@petton.fr>, 22744@debbugs.gnu.org
Subject: bug#22744: 24.5; url-retrieve callback is not invoked when http response content is empty
Date: Mon, 22 Feb 2016 14:03:00 +1100 [thread overview]
Message-ID: <87bn79zbtn.fsf@gnus.org> (raw)
In-Reply-To: <CAJQX3DwP_2=Du26N_C1JY5zBtTGyYQszTizBMDNrJ_7912V+tA@mail.gmail.com> (Shiyao Ma's message of "Sun, 21 Feb 2016 18:51:28 +0800")
Shiyao Ma <i@introo.me> writes:
> I installed from the git head.
>
> For the callback status, it's:
> (:error (error http 405) :redirect https://bpaste.net/show/9f7b83e91ebc)
>
> For the callback buffer, it's:
> HTTP/1.1 405 METHOD NOT ALLOWED
> Server: nginx
[...]
> So from the url-debug output, the logic is doing wrong. On Line#30, it's doing
> a *redirect* with post, resulting an HTTP 405.
So that web site wants the redirect to be done with GET instead of POST?
I don't know what the standard says should happen here...
Nicolas, could you look into this? The issue is that when POST-ing to
bpaste.net, it 302 redirects...
> BTW, possible to do nothing other than firing up the callback when receiving
> the HTTP 302 on Line#32 ?
No, the callbacks are fired after landing on the final URL after all the
redirects.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2016-02-22 3:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 5:09 bug#22744: 24.5; url-retrieve callback is not invoked when http response content is empty Shiyao Ma
2016-02-20 7:41 ` Lars Ingebrigtsen
2016-02-20 11:15 ` Shiyao Ma
2016-02-21 2:57 ` Lars Ingebrigtsen
2016-02-21 10:51 ` Shiyao Ma
2016-02-22 3:03 ` Lars Ingebrigtsen [this message]
2019-09-24 8:14 ` Lars Ingebrigtsen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87bn79zbtn.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=22744@debbugs.gnu.org \
--cc=i@introo.me \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).