Bug 110552 - mod_proxy breaks windowsupdate.microsoft.com
Summary: mod_proxy breaks windowsupdate.microsoft.com
Alias: None
Product: Fedora
Classification: Fedora
Component: httpd   
(Show other bugs)
Version: 1
Hardware: i386
OS: Linux
Target Milestone: ---
Assignee: Joe Orton
QA Contact:
Depends On:
TreeView+ depends on / blocked
Reported: 2003-11-21 01:23 UTC by Brian Baggett
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-10-28 15:04:09 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Brian Baggett 2003-11-21 01:23:23 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5)

Description of problem:
This is the httpd bug from

"Apache2 proxy seems to drop Content-Length header from replies to
HEAD requests. This is very bad for Microsoft's Windows Update system
(and against HTTP spec). The problem is caused by CONTENT_LENGTH
output filter setting Content-Length header to zero because there is
no body data. Later on Apache removes Content-Length header if it has
value 0. The attached patch fixes the problem in CONTENT_LENGTH output
filter by preventing it from modifying the content length of a reply
to HEAD request. The attached patch is against HEAD of
APACHE_2_0_BRANCH as of this morning."

URL: http://www.mail-archive.com/dev@httpd.apache.org/msg16088.html

I backported the patch listed in the diff as a part of my own RPM and
rebuilt it.  It works as expected then.

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

How reproducible:

Steps to Reproduce:
Load up httpd with the proxy enabled.  Go to
Windowsupdate.microsoft.com.  Watch it error out with error
#0x80072f76.  Rebuild with the above patch and it will work fine.

Additional info:

Comment 1 Joe Orton 2003-11-21 08:49:25 UTC
This should be fixed in 2.0.48 - can you try the 2.0.48 updates?


Comment 2 Brian Baggett 2003-11-21 14:19:34 UTC
I first pulled the httpd-2.0.48-1.2 RPM from
and tried it unpatched and it doesn't work.  When that happened, I got
the SRPM and the patch I referenced from CVS did not make it in to
protocol.c.  After adding it, it worked just like 2.0.47 did.  But
2.0.48 is still broken in this regard by default.

Comment 3 Matthew Miller 2006-07-11 17:21:30 UTC
Fedora Core 1 is maintained by the Fedora Legacy project for security updates
only. If this problem is a security issue, please reopen and reassign to the
Fedora Legacy product. If it is not a security issue and hasn't been resolved in
the current FC5 updates or in the FC6 test release, reopen and change the
version to match.


NOTE: Fedora Core 1 is reaching the final end of support even by the Legacy
project. After Fedora Core 6 Test 2 is released (currently scheduled for July
26th), there will be no more security updates for FC1. Please use these next two
weeks to upgrade any remaining FC1 systems to a current release.

Comment 4 John Thacker 2006-10-28 15:04:09 UTC
Closing per lack of response to the previous comment.  Note that FC1 and FC2 are
no longer supported even by Fedora Legacy.  If this bug still occurs on FC3 or
FC4, please assign to that version and Fedora Legacy.  If it still occurs on FC5
or FC6, please reopen and assign to the correct version.

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