Bug 143984
Summary: | yum update fails to download headers through proxy | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Davide Bolcioni <dblistsub-redzilla> |
Component: | yum | Assignee: | Jeremy Katz <katzj> |
Status: | CLOSED NOTABUG | QA Contact: | |
Severity: | medium | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | CC: | dblistsub-redzilla, katzj |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2005-01-07 11:13:25 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Davide Bolcioni
2005-01-03 11:27:35 UTC
Sorry, my mistake. The gateway is multihomed and the value of *_proxy was not correct; wget got it right because the appropriate value was in /etc/wgetrc. Sorry again, too eager. Even with the correct proxy, new headers get [Error -1] Header is not complete. does your proxy not support byte-ranges? Great suggestion: the squid.conf was too paranoid and overused header_access, silently strangling byte range functionality. Allowing through the appropriate HTTP/1.1 headers did the trick. Thank you very much. |