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 15:08:37 +0100	[thread overview]
Message-ID: <20190904140837.GA6282@toaster> (raw)
In-Reply-To: <20190803161036.eklhad@comcast.net>

On Tue, Sep 03, 2019 at 04:10:36PM -0400, Karl Dahlke wrote:
> This happens on my relatively old machine and on a newer machine.
> In edbrowse and with db4
> e http://iyfsearch.com/px.js?ch=2
> 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.
> e http://iyfsearch.com/px.js?ch=2
> 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 gives?

On my machine (Debian sid updated as of... a few days ago I think):
curl --head -vv http://iyfsearch.com/px.js?ch=2
*   Trying
* Connected to iyfsearch.com ( port 80 (#0)
> HEAD /px.js?ch=2 HTTP/1.1
> Host: iyfsearch.com
> User-Agent: curl/7.65.3
> Accept: */*
* Recv failure: Connection reset by peer
* Closing connection 0
curl: (56) Recv failure: Connection reset by peer

curl --version
curl 7.65.3 (x86_64-pc-linux-gnu) libcurl/7.65.3 OpenSSL/1.1.1c zlib/1.2.11
libidn2/2.2.0 libpsl/0.20.2 (+libidn2/2.0.5) libssh2/1.8.0 nghttp2/1.39.2
Release-Date: 2019-07-19
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3
pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp
Features: AsynchDNS GSS-API HTTP2 HTTPS-proxy IDN IPv6 Kerberos Largefile

> What happens when other browsers issue head requests?

Dunno, but my guess is this site'll reset the connection on them as well...
very odd.  However, in my experience (my day job is developing a web
security service) there are some very odd HTTP implementations out there.
My guess is that server simply cannot handle HEAD requests and, rather than
speaking correct HTTP, just drops the connection.  That being said, it may
be worth trying with a different user agent (I've seen that kind of oddness
before as well).


  reply	other threads:[~2019-09-04 14: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 [this message]
2019-09-04 15:03   ` Karl Dahlke
2019-09-04 15:08     ` Adam Thompson

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=20190904140837.GA6282@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).