caching problem with wget used by MacPorts infrastructure

[Marko Käning]

Hi Joshua,

> 1. MacPorts doesn't use wget.
oops, how did I get the idea that wget is used? Strange. :-)

> 2. The server needs to be configured to use appropriate Cache-Control
> headers (and Etags etc) to stop content from being incorrectly cached.
Ah, ok, so it's surely a server misconfiguration on BitBucket's end then...

> Answer:
> 
> Libcurl actually sends Pragma: no-cache by default, but we clear it in
> our code in curl.c, and there's no runtime config to turn it back on. So
> if you really need that, editing the source is the only way.
Oh, ok, if you clear the no-cache then you simply have to run into this trap if the remote server has that caching problem.

Thanks for clarifying this for me. :-)

Greets,
Marko