From: coroa@online.de (Jonas Hörsch)
To: 13598@debbugs.gnu.org
Subject: bug#13598: 24.3.50; url-http.el doesn't correctly parse headers when they are sent line-by-line
Date: Thu, 07 Feb 2013 19:13:40 +0100 [thread overview]
Message-ID: <87wquk3sbv.fsf@online.de> (raw)
In-Reply-To: <87d2wluuu9.fsf@online.de>
On Thu, Jan 31 2013, Jonas Hoersch wrote:
> changing the regex in (re-search-forward "^\r*$" nil t) to "^\r*\n"
> solves the problem for me, but i'm unsure about what i might possibly be
> breaking that way.
i'm positive now, that changing the regex to "^\r+$" is the way to go.
i would be happy to supply a patch, but i understand it is probably to
trivial a matter to justify going through the legal requirements first.
the following advice can serve as a hotfix:
(defadvice url-http-wait-for-headers-change-function (around
url-http-properly-wait-for-headers-advice
activate)
(save-excursion
(goto-char (point-min))
(if (re-search-forward "^\r+$" nil t)
ad-do-it
(url-http-debug "Incomplete headers...: %d" (point-max)))))
next prev parent reply other threads:[~2013-02-07 18:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-31 17:26 bug#13598: 24.3.50; url-http.el doesn't correctly parse headers when they are sent line-by-line Jonas Hoersch
2013-02-07 18:13 ` Jonas Hörsch [this message]
2013-02-13 17:19 ` Bastien
2013-02-13 19:30 ` Stefan Monnier
2013-02-13 19:42 ` Glenn Morris
2013-02-13 21:38 ` Glenn Morris
2013-02-14 6:08 ` Bastien
2013-02-16 2:06 ` Glenn Morris
2014-02-26 9:32 ` bug#13598: 24.3.50; Blazej Adamczyk
2014-02-26 16:54 ` bug#13598: 24.3.50 Blazej Adamczyk
2014-02-27 22:43 ` Glenn Morris
2014-03-03 6:10 ` Blazej Adamczyk
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=87wquk3sbv.fsf@online.de \
--to=coroa@online.de \
--cc=13598@debbugs.gnu.org \
/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).