git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: HTTP repo referencing stale heads (can't clone)

From
RSRadoslaw Szkodzinski <astralstorm@o2.pl>
Date
Apr 5, 2006, 12:23 UTC
Message-ID
<4433B6AA.6070407@o2.pl>
In-Reply-To
<20060404180130.GF14967@reactrix.com>
Nick Hengeveld wrote:
Show 16 quoted lines
> On Mon, Apr 03, 2006 at 07:28:28PM +0100, Daniel Drake wrote:
> 
>> Ah, should have known. I am behind a (lame) transparent proxy on port 80.
>>
>> I opened that file in my web browser and it showed the old heads. After 
>> a force-refresh (ctrl+F5, which sends some additionally http headers to 
>> refresh the page from the real server), the old heads disappeared, and 
>> git now clones successfully.
>>
>> git-http-fetch should probably send those extra headers too. I'll try to 
>> find some time to look at this next week.
> 
> git-http-fetch uses the "Pragma: no-cache" header when requesting
> objects that shouldn't be cached.  Is this the additional header you're
> referring to?
> 
As per HTTP 1.1, it should also send:
Cache-Control: no-cache
Pragma: no-cache is the deprecated extension.
It's safe to send both.
-- 
GPG Key id:  0xD1F10BA2
Fingerprint: 96E2 304A B9C4 949A 10A0  9105 9543 0453 D1F1 0BA2

AstralStorm
Previous: Nick Hengeveld
Message 11 of 11 in “HTTP repo referencing stale heads (can't clone)”
  1. Daniel DrakeApr 3, 2006
  2. Junio C HamanoApr 3, 2006
  3. Nick HengeveldApr 3, 2006
  4. Junio C HamanoApr 4, 2006
  5. Petr BaudisApr 4, 2006
  6. Nick HengeveldApr 4, 2006
  7. Petr BaudisApr 4, 2006
  8. Nick HengeveldApr 4, 2006
  9. Daniel DrakeApr 3, 2006
  10. Nick HengeveldApr 4, 2006
  11. Radoslaw SzkodzinskiApr 5, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.