From: Karl Dahlke <firstname.lastname@example.org>
Subject: [edbrowse-dev] Another curl question
Date: Tue, 03 Sep 2019 16:10:36 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
This happens on my relatively old machine and on a newer machine.
In edbrowse and with db4
It asks if you want to download, just hit space to pull it into memory.
It is a regular fetch and it goes into cache. No problem.
Quit edbrowse and bring it up again. db4 and do the same thing.
It sees it in cache and just does a head request.
The server should give you the same etag and you pull it out of cache, but,
curl says "could not read the data from the server"
Thus the file is not fetched at all
It looks like we get all the right stuff from the server.
What happens when other browsers issue head requests?
next reply other threads:[~2019-09-03 20:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 20:10 Karl Dahlke [this message]
2019-09-04 14:08 ` Adam Thompson
2019-09-04 15:03 ` Karl Dahlke
2019-09-04 15:08 ` Adam Thompson
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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.
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 NNTP newsgroup(s).