Molle Bestefich wrote:
>Rainer Müller wrote:
>
>
>>>Solutions to the problem are straightforward:
>>> 1. Tell everyone to flush their caches before downloading (cumbersome).
>>> 2. Add "Pragma: No-Cache" headers to the HTTP headers when files are
>>>downloaded from the nightly directory. This would cause browsers to
>>>avoid caching the files.
>>>
>>>
>
>Is there anyone who has access to the Apache config who could add this?
>
>
>
>>> 3. Rename at least the .msi file when compiling. I'd prefer it to
>>>include the number of the revision it's compiled from, as I save it to
>>>disk using this number anyway.
>>>
>>>
>
>Would including the wc rev in the filename be easy to do?
>
>
>
>>4. Use a better browser that does not fool you ;-)
>>
>>
>
>I'm using Firefox 1.0.2.
>
>
>
>>No, seriously: I have no problems with the nightlies at all. I'm
>>downloading them with Firefox. Normally you should recognize if your
>>browser is downloading or not or do you have such a fast connection?
>>
>>
>
>4MB/s. Hardly noticeable, I'd say.
>
>Maybe you do not download nightlies often enough, or your cache is
>smaller than mine, and it happens to be flushed before you next try a
>download?
>
>
>
>>Do you use a Proxy which maybe invokes the caching?
>>
>>
>
>I'm not, Peter might be.
>I just checked Firefox' behaviour using a HTTP sniffer.
>When the .MSI is in Firefox's cache, the browser doesn't even contact
>the HTTP server to check if the file has been modified; thus proxying
>has nothing to do with it.
>
>
>
I'm using Firefox 1.0.2 as well, on a good cable.
Thats an interesting comment about Firefox not contacting again. I'm
surprised the date differences between the remote and cached cached
versions doesn't trigger a download.
Bug in 1.0.2 anyone??
Peter
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Sun Mar 27 13:51:40 2005