Bug 11942

Summary: Problems with transparent proxies
Product: [Retired] Red Hat Linux Reporter: h0e <hoshem>
Component: up2dateAssignee: Preston Brown <pbrown>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 6.2   
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2000-06-07 09:17:45 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 h0e 2000-06-07 09:17:44 UTC 
When up2date is configured not to use proxies, but port 80 traffic is
transparently sent through a proxy at the isp, bad things can happen,
because up2date doesn't specify in the http traffic what host the request
is for (unless configured to use a manual proxy), and transparent proxies
(like my isp's) can think the request is for themselves, and will return a
404 not found error. Perhaps up2date should, instead of sending a "POST
/cgi-bin/server.cgi HTTP/1.0" request, send a "POST
http://priority.redhat.com/cgi-bin/server.cgi HTTP/1.0" (for example)
whether it is configured to use proxies or not?
Comment 1 Preston Brown 2000-11-27 21:01:59 UTC 
the update agent from7.0 will shortly be released for 6.x, and it includes this
feature.
Comment 2 Jay Turner 2001-03-01 13:09:09 UTC 
Up2date is now sending the following to the server:

"POST https://www.rhns.redhat.com/XMLRPC HTTP/1.0"

So that should take care of the problems related in this posting.

Closing out this issue.