GNU bug report logs -
#35927
26.2; url-http-end-of-headers sets to 1 when cache is working
Previous Next
Reported by: Xu Chunyang <mail <at> xuchunyang.me>
Date: Mon, 27 May 2019 14:48:02 UTC
Severity: normal
Tags: notabug
Found in version 26.2
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
Full log
View this message in rfc822 format
Today I enable URL cache via
(setq url-automatic-caching t
url-cache-expire-time (* 6 3600))
and I notice url-http-end-of-headers isn't the end of the headers when
cache is working. This breaks some of my code, I assume it is the end of
the header so I use (goto-char url-http-end-of-headers) before parsing
the response body. Is this expected or a bug?
(with-current-buffer (url-retrieve-synchronously "http://example.com")
(message "=> %S" url-http-end-of-headers))
"=> #<marker at 347 in *http example.com:80*>"
(with-current-buffer (url-retrieve-synchronously "http://example.com")
(message "=> %S" url-http-end-of-headers))
"=> #<marker at 1 in *http example.com:80*-325608>"
(with-current-buffer (url-retrieve-synchronously "http://example.com")
(message "=> %S" url-http-end-of-headers))
"=> #<marker at 1 in *http example.com:80*-887290>"
This bug report was last modified 5 years and 302 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.