[Bug 476080] New: zypper refresh should try to avoid proxy cache
https://bugzilla.novell.com/show_bug.cgi?id=476080 Summary: zypper refresh should try to avoid proxy cache Classification: openSUSE Product: openSUSE 11.2 Version: Alpha 0 Platform: Other OS/Version: Other Status: NEW Severity: Major Priority: P5 - None Component: libzypp AssignedTo: zypp-maintainers@forge.provo.novell.com ReportedBy: dominique.leuenberger@tmf-group.com QAContact: qa@suse.de Found By: --- Issue at hand: - using zypper behind a caching proxy - issued zypper ref (which works fine). -> saw that my repo is outdated, so I updated it on the server - zypper ref (does not do what expected, as it get's cached info from the proxy). I think at least zypper ref should try to overrule the proxy cache The header sent to get repomd.xml was: GET http://download.videolan.org/pub/videolan/vlc/SuSE/11.2/repodata/repomd.xml HTTP/1.1 User-Agent: ZYpp 5.25.0 (curl 7.19.0) Host: download.videolan.org Accept: */* Proxy-Connection: Keep-Alive X-ZYpp-AnonymousId: a3d1e58a-9b86-11dd-858e-001d09db9ce1 Due to this caching, the repo is now 'broken' for me until the cache releases it. (obvious: old files referenced in metadata, new ones on server, with old ones dropped). Severity Major, as this is actually an issue for all proxy users I guess. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=476080 User ma@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=476080#c1 Michael Andres <ma@novell.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P4 - Low CC| |dmacvicar@novell.com, | |jkupec@novell.com, | |ma@novell.com --- Comment #1 from Michael Andres <ma@novell.com> 2009-02-27 05:14:21 MST --- Hmm. I'm not sure whether this is a zypper/libzypp issue. If the proxy returns cached data although the original data changed, I'd consider it a proxy issue. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=476080 User dominique.leuenberger@tmf-group.com added comment https://bugzilla.novell.com/show_bug.cgi?id=476080#c2 --- Comment #2 from Dominique Leuenberger <dominique.leuenberger@tmf-group.com> 2009-02-27 05:20:56 MST --- (In reply to comment #1)
Hmm. I'm not sure whether this is a zypper/libzypp issue. If the proxy returns cached data although the original data changed, I'd consider it a proxy issue.
I don't agree this being a proxy issue. The point of the proxy is to give the fast reply to all users in the network by caching the sites, without requesting the site at every request. In case you want to override the proxy cache, you can always inject the headers
Pragma: no-cache Cache-control: no-cache
which will instruct every (compliant and good) proxy to fetch the site from the net. This is actually even what is added when you press F5 (or CTRL-R) in a browser to refresh the page: normall requests without those headers, giving the control to the proxy, on a Refresh including those headers, intructing the proxy to ignore it's cache and to rebuild it. In case you consider it a 'bug of the proxy', you can assign this bug internally to another Novell group: It's a Border Manager :) -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=476080 User ma@novell.com added comment https://bugzilla.novell.com/show_bug.cgi?id=476080#c3 --- Comment #3 from Michael Andres <ma@novell.com> 2009-03-16 06:25:10 MST --- @Jano,Duncan: What do you think about a media backend no-proxy option (globaly, not per request)? Would not be hard to implement and zypper could easily offer a --no-proxy option. So one can at least workaround this. Somewhat dislike to turn of proxy per default while refresh. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=476080 User dominique.leuenberger@tmf-group.com added comment https://bugzilla.novell.com/show_bug.cgi?id=476080#c4 --- Comment #4 from Dominique Leuenberger <dominique.leuenberger@tmf-group.com> 2009-03-16 06:28:47 MST --- (In reply to comment #3)
@Jano,Duncan: What do you think about a media backend no-proxy option (globaly, not per request)? Would not be hard to implement and zypper could easily offer a --no-proxy option. So one can at least workaround this. Somewhat dislike to turn of proxy per default while refresh.
Pragma: no-cache Cache-control: no-cache That's header to be sent inside the http requests. They will be interpreted by
that goes in the wrong direction here. I do NOT request the proxy to be disabled when refreshing or alike... (this would not work in any proxied environment anyhow), BUT to give the correct headers to force a refresh also of the proxy cache: the proxy. But still: it HAS to be sent TO the proxy... (so --no-proxy would break the refresh completely... as http servers here are not reachable without requesting it through the proxy). -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com