edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@edbrowse.org
Subject: Re: [edbrowse-dev] Another curl question
Date: Wed, 4 Sep 2019 16:08:27 +0100	[thread overview]
Message-ID: <20190904150827.GB6282@toaster> (raw)
In-Reply-To: <20190804110326.eklhad@comcast.net>

On Wed, Sep 04, 2019 at 11:03:26AM -0400, Karl Dahlke wrote:
> > My guess is that server simply cannot handle HEAD requests and, rather than
> Right, so, I now revert back to get upon curl head failure; I use to just give up.
> Least this way you get your data, even if it didn't come from cache.

That'll work and sounds sensible.  I also wonder about the possibility of exposing the curl debug messages, perhaps at some debug level.

      reply	other threads:[~2019-09-04 15:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-03 20:10 Karl Dahlke
2019-09-04 14:08 ` Adam Thompson
2019-09-04 15:03   ` Karl Dahlke
2019-09-04 15:08     ` Adam Thompson [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190904150827.GB6282@toaster \
    --to=arthompson1990@gmail.com \
    --cc=edbrowse-dev@edbrowse.org \
    --cc=eklhad@comcast.net \


* 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).