Bug 218282 - yum update fails against Roxen webserver
yum update fails against Roxen webserver
Product: Fedora
Classification: Fedora
Component: python-urlgrabber (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: James Antill
Depends On:
  Show dependency treegraph
Reported: 2006-12-04 08:12 EST by Anders Blomdell
Modified: 2008-05-06 13:06 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2008-05-06 13:06:41 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
only get requested amount of bytes (1.40 KB, patch)
2006-12-04 08:12 EST, Anders Blomdell
no flags Details | Diff

  None (edit)
Description Anders Blomdell 2006-12-04 08:12:19 EST
Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:


Steps to Reproduce:
1. Try to run yum against a http repository on a Roxen webserver
Actual results:

yum timeouts

Expected results:

installation of requested packages

Additional info:

The problem is that urlgrabber does this request:

  GET /path/to/some.rpm HTTP/1.1
  Host: www
  Accept-Encoding: identity
  Range: bytes=280-545669
  User-agent: urlgrabber/2.9.9

And this is the response from the server:

  HTTP/1.1 206 OK
  Accept-Ranges: bytes
  Server: Roxen/4 5 78-release1
  Last-Modified: Tue, 01 Nov 2005 14:38:04 GMT
  Vary: *
  Content-Range: bytes 280-545669/55570308
  Date: Mon, 04 Dec 2006 10:24:25 GMT
  Content-Type: audio/x-pn-realaudio-plugin
  Connection: keep-alive

The problem is that urlgrabber tries to read more than the requested amount of
bytes, and Roxen keeps the connection open, therefore the connection times out.
Comment 1 Anders Blomdell 2006-12-04 08:12:19 EST
Created attachment 142728 [details]
only get requested amount of bytes
Comment 2 Bug Zapper 2008-04-04 01:05:38 EDT
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.

If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.

If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
the change.

Thanks for your help, and we apologize again that we haven't handled
these issues to this point.

The process we are following is outlined here:

We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.

And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
Comment 3 Bug Zapper 2008-05-06 13:06:40 EDT
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.