From: Lars Ingebrigtsen <larsi@gnus.org>
To: Andreas Politz <politza@hochschule-trier.de>
Cc: 26063@debbugs.gnu.org
Subject: bug#26063: 26.0.50; url-insert-file-contents signals error for HTTP 304 response
Date: Wed, 15 May 2019 07:41:12 +0200 [thread overview]
Message-ID: <87v9ycuvev.fsf@mouse.gnus.org> (raw)
In-Reply-To: <87shmjwtkw.fsf@luca> (Andreas Politz's message of "Sat, 11 Mar 2017 19:34:39 +0100")
Andreas Politz <politza@hochschule-trier.de> writes:
> Start from emacs -Q .
>
> 1. Install debbugs (http://elpa.gnu.org/packages/debbugs.html)
> 2. Enable url-automatic-caching
> 3. M-x debbugs-gnu-search RET change-group RET
>
> This should pop-up some results in a new buffer. Now hit RET
> (debbugs-gnu-select-report) on one of them, which will popup a gnus
> buffer displaying the related articles. Close that buffer via q
> (gnus-summary-exit). Back in the debbugs buffer, hit RET again, which
> will lead to the following (abbreviated) backtrace.
>
> Debugger entered--Lisp error: (file-error
> "http://debbugs.gnu.org/cgi/bugreport.cgi?bug=23906;mboxmaint=yes;mboxstat=yes"
> "Not modified")
This seems to work for me in Emacs 27.
> I think url-insert-file-contents should not raise an error when the
> status code is 304, because it just means that the result comes from the
> cache, instead of the server.
Yup. I seem to recall somebody else fixing the status code issue a
while back. Is this still a problem for you?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-05-15 5:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-11 18:34 bug#26063: 26.0.50; url-insert-file-contents signals error for HTTP 304 response Andreas Politz
2019-05-15 5:41 ` Lars Ingebrigtsen [this message]
2019-06-30 0:25 ` Basil L. Contovounesios
2019-07-04 13:39 ` Lars Ingebrigtsen
2019-09-24 8:43 ` 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=87v9ycuvev.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=26063@debbugs.gnu.org \
--cc=politza@hochschule-trier.de \
/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).