Description of problem: I just noticed that yum downloaded nearly 90 megabytes of headers for openoffice.org-core package. The .hdr file is only 440 bytes smaller than the whole package (440 is the start entry for the header in primary.xml) Version-Release number of selected component (if applicable): 3.0.1-2 How reproducible: It does it again when after I removed openoffice.org-core with rpm --nodeps -e Steps to Reproduce: 1. rpm --nodeps -e openoffice.org-core 2. rm /var/cache/yum/updates/headers/openoffice.org-core 3. yum install openoffice.org-core 4. $ ls -la /var/cache/yum/updates/headers/openoffice.org-core-2.0.4-5.5.10.i386.hdr Actual results: Downloads around 90 megs of headers: -rw-r--r-- 1 root root 92258305 3. Jan 19:21 /var/cache/yum/updates/headers/openoffice.org-core-2.0.4-5.5.10.i386.hdr Expected results: the filesize of the header should be only 443149 bytes.
1. what mirror was it using? 2. are you, by chance, behind a proxy server of some kind?
(In reply to comment #1) > 1. what mirror was it using? On from mirrorlist=http://mirrors.fedoraproject.org/mirrorlist?repo=updates-released-fc$releasever&arch=$basearch Is the used mirror somewhere stored or do I have to sniff the traffic to get the information? > 2. are you, by chance, behind a proxy server of some kind? I am using a http_proxy, that appeears to be a squid/2.5.STABLE4
okay. Check with the proxy admin - see if they are allowing http 1.1 byte ranges through the proxy. If they are not then there is the problem.
(In reply to comment #3) > okay. Check with the proxy admin - see if they are allowing http 1.1 byte ranges > through the proxy. If they are not then there is the problem. I wrote a mail to the admin. With other packages it seems to work and for the openoffice.org-core package yum skips the first 440 bytes as it is told in primary.xml - is this done with byte ranges, too, or is it yum that just does not store these bytes? And in case that the proxy server does not support byte ranges, is it easily possible to make yum close the http connection when it got the full header instead of relying on the server to send only the wanted data?
(In reply to comment #3) > okay. Check with the proxy admin - see if they are allowing http 1.1 byte ranges > through the proxy. Do you know which option in squid.conf this could be? The only related option I found is: # range_offset_limit 0 KB which has the default value on the proxy.
With F7, we're not doing the header downloads anymore so this should be resolved there