[zypp-devel] libzypp client special behaviour for Factory?
Hi, I hear that factory installs force no-cache pragma, which destroys any cacheability. Is that (still) so? Or is that outdated information? If yes, this should be regarded as workaround of the past and removed. Thanks, Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
Hi, On Tue, 2 Sep 2008, Peter Poeml wrote:
I hear that factory installs force no-cache pragma, which destroys any cacheability.
Is that (still) so? Or is that outdated information?
When I grep for CURLOPT_HTTPHEADER I see no matches in libzypp, and I think that's the only way to actually set a "Pragma: no-cache" header, right? (at least I can't find any CURLOPT_* that would directly set that header). I hence assume that this is outdated information. Ciao, Michael. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Hi Micha, On Tue, Sep 02, 2008 at 03:04:58PM +0200, Michael Matz wrote:
On Tue, 2 Sep 2008, Peter Poeml wrote:
I hear that factory installs force no-cache pragma, which destroys any cacheability.
Is that (still) so? Or is that outdated information?
When I grep for CURLOPT_HTTPHEADER I see no matches in libzypp, and I think that's the only way to actually set a "Pragma: no-cache" header, right? (at least I can't find any CURLOPT_* that would directly set that header).
I seem to remember that libcurl adds the header by default on itself. And I think there was actually a bug about it. The curl commandline tool definitely does this.
I hence assume that this is outdated information.
Ciao, Michael.
Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
Dňa Tuesday 02 September 2008 15:06:25 Peter Poeml ste napísal:
Hi Micha,
On Tue, Sep 02, 2008 at 03:04:58PM +0200, Michael Matz wrote:
On Tue, 2 Sep 2008, Peter Poeml wrote:
I hear that factory installs force no-cache pragma, which destroys any cacheability.
Is that (still) so? Or is that outdated information?
When I grep for CURLOPT_HTTPHEADER I see no matches in libzypp, and I think that's the only way to actually set a "Pragma: no-cache" header, right? (at least I can't find any CURLOPT_* that would directly set that header).
I seem to remember that libcurl adds the header by default on itself. And I think there was actually a bug about it.
The curl commandline tool definitely does this.
Bug 326208 - libcurl forces "pragma: no-cache" which makes libzypp not play well with squid ? Stano -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
On Tue, Sep 02, 2008 at 03:12:51PM +0200, Stanislav Visnovsky wrote:
Dňa Tuesday 02 September 2008 15:06:25 Peter Poeml ste napísal:
Hi Micha,
On Tue, Sep 02, 2008 at 03:04:58PM +0200, Michael Matz wrote:
On Tue, 2 Sep 2008, Peter Poeml wrote:
I hear that factory installs force no-cache pragma, which destroys any cacheability.
Is that (still) so? Or is that outdated information?
When I grep for CURLOPT_HTTPHEADER I see no matches in libzypp, and I think that's the only way to actually set a "Pragma: no-cache" header, right? (at least I can't find any CURLOPT_* that would directly set that header).
I seem to remember that libcurl adds the header by default on itself. And I think there was actually a bug about it.
The curl commandline tool definitely does this.
Bug 326208 - libcurl forces "pragma: no-cache" which makes libzypp not play well with squid
?
Yes, that's the one. Thanks for digging it out. So it seems this is not fixed yet. I was asking because I got a report from a mirror / site admin who needed to work around in squid by making it ignore the header. A university network with lots of openSUSE deployments. Peter -- "WARNING: This bug is visible to non-employees. Please be respectful!" SUSE LINUX Products GmbH Research & Development
Hi, On Tue, 2 Sep 2008, Peter Poeml wrote:
Is that (still) so? Or is that outdated information?
When I grep for CURLOPT_HTTPHEADER I see no matches in libzypp, and I think that's the only way to actually set a "Pragma: no-cache" header, right? (at least I can't find any CURLOPT_* that would directly set that header).
I seem to remember that libcurl adds the header by default on itself.
How crappy is that? Bah.
And I think there was actually a bug about it.
bug #326208, indeed. Still open. And google also indicates that this still is the case with newest libcurl. Blaeh. Reading the libcurl sources it seems to add the no-cache header under these conditions: (!checkheaders(data, "Pragma:") && (conn->bits.httpproxy && !conn->bits.tunnel_proxy) )? "Pragma: no-cache\r\n":NULL; I.e. only if there's a proxy, but not tunneling through it. Still seems fragile. Ciao, Michael. -- To unsubscribe, e-mail: zypp-devel+unsubscribe@opensuse.org For additional commands, e-mail: zypp-devel+help@opensuse.org
Michael Matz escribió:
Hi,
On Tue, 2 Sep 2008, Peter Poeml wrote:
Is that (still) so? Or is that outdated information? When I grep for CURLOPT_HTTPHEADER I see no matches in libzypp, and I think that's the only way to actually set a "Pragma: no-cache" header, right? (at least I can't find any CURLOPT_* that would directly set that header). I seem to remember that libcurl adds the header by default on itself.
How crappy is that? Bah.
This is IMHO a bug, or at least a misfeature, should be up to the application to send this header or not.
I.e. only if there's a proxy, but not tunneling through it. Still seems fragile.
We need to figure why it is doing this, there must be a valid reason, however I cant quite figure it. -- "A computer is like an Old Testament god, with a lot of rules and no mercy. " Cristian Rodríguez R. Platform/OpenSUSE - Core Services SUSE LINUX Products GmbH Research & Development http://www.opensuse.org/
participants (4)
-
Cristian Rodríguez -
Michael Matz -
Peter Poeml -
Stanislav Visnovsky