All of lore.kernel.org
 help / color / mirror / Atom feed
From: Radoslaw Szkodzinski <astralstorm@o2.pl>
To: Nick Hengeveld <nickh@reactrix.com>
Cc: Daniel Drake <dsd@gentoo.org>, Junio C Hamano <junkio@cox.net>,
	git@vger.kernel.org
Subject: Re: HTTP repo referencing stale heads (can't clone)
Date: Wed, 05 Apr 2006 14:23:06 +0200	[thread overview]
Message-ID: <4433B6AA.6070407@o2.pl> (raw)
In-Reply-To: <20060404180130.GF14967@reactrix.com>

[-- Attachment #1: Type: text/plain, Size: 988 bytes --]

Nick Hengeveld wrote:
> 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


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 254 bytes --]

      reply	other threads:[~2006-04-05 12:28 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-03 16:01 HTTP repo referencing stale heads (can't clone) Daniel Drake
2006-04-03 17:23 ` Junio C Hamano
2006-04-03 18:09   ` Nick Hengeveld
2006-04-04  7:03     ` Junio C Hamano
2006-04-04 10:00     ` Petr Baudis
2006-04-04 12:10       ` Nick Hengeveld
2006-04-04 15:27         ` Petr Baudis
2006-04-04 17:56           ` Nick Hengeveld
2006-04-03 18:28   ` Daniel Drake
2006-04-04 18:01     ` Nick Hengeveld
2006-04-05 12:23       ` Radoslaw Szkodzinski [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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

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

  git send-email \
    --in-reply-to=4433B6AA.6070407@o2.pl \
    --to=astralstorm@o2.pl \
    --cc=dsd@gentoo.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=nickh@reactrix.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.