From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from resqmta-ch2-03v.sys.comcast.net (resqmta-ch2-03v.sys.comcast.net [IPv6:2001:558:fe21:29:69:252:207:35]) by hurricane.the-brannons.com (Postfix) with ESMTPS id 46FDC77AA1 for ; Tue, 3 Sep 2019 13:10:39 -0700 (PDT) Received: from resomta-ch2-06v.sys.comcast.net ([69.252.207.102]) by resqmta-ch2-03v.sys.comcast.net with ESMTP id 5DGbi5BNIO4k25F8Qi75Nt; Tue, 03 Sep 2019 20:10:38 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=20190202a; t=1567541438; bh=Rehd7dKNgny6X6H5Lclqh2mC+blLCl4v2EUyLu4ZJgI=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=wHfRaCEm4GGXtHXQ2KpiiZ3KYxA671rEFFk0hU2GrUar46ZQEJb2GlRVRL28J5iny ayPojkClNDeFtIk4KQiwaNVOyEOZhjEIYefHXfvDNeEK1zTt+0UcTyk42RIsFvfoY/ 6B2K5BHpgfLnCxGk2Gf7faofSPnlR2yUW5YT2/G4m2w9BkyYSPLe1I7tVA0EnVXk9+ qP0Dh8aZgLgR5rGK8N99QK8wMkFSkur3tpizaWJjFQ1Dbf9Z18GXD7HdwNSa2nRuYP DnfdpcqhekYuC8BUe06Spj4fmaQ57GO9hhKvbhXTA+mArQHRBPaNf1XagEqbbb3FpZ HrAN/gEubFWew== Received: from unknown ([IPv6:2601:408:c303:3f49:21e:4fff:fec2:a0f1]) by resomta-ch2-06v.sys.comcast.net with ESMTPSA id 5F8OiEUnGk31s5F8PiPSon; Tue, 03 Sep 2019 20:10:37 +0000 X-Xfinity-VMeta: sc=0;st=legit To:edbrowse-dev@edbrowse.org From: Karl Dahlke Reply-to: Karl Dahlke User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/5.0; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E) Subject: [edbrowse-dev] Another curl question Date: Tue, 03 Sep 2019 16:10:36 -0400 Message-ID: <20190803161036.eklhad@comcast.net> X-BeenThere: edbrowse-dev@edbrowse.org List-Id: Edbrowse Development List Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit 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? What happens when other browsers issue head requests? Karl Dahlke