Bug 670447

Summary:	Curl fails on redirect with explicit Host Header.
Product:	Red Hat Enterprise Linux 4	Reporter:	DCS <dcarrillo>
Component:	curl	Assignee:	Kamil Dudka <kdudka>
Status:	CLOSED WONTFIX	QA Contact:	BaseOS QE Security Team <qe-baseos-security>
Severity:	medium	Docs Contact:
Priority:	low
Version:	4.8	CC:	ovasik, prc
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2011-01-18 11:55:37 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description DCS 2011-01-18 10:40:05 UTC

Description of problem:

When using an explicit host header -H "Host: <fqdn>", if the response is 302 the redirection doesn't work.

Version-Release number of selected component (if applicable):
curl-7.12.1-11.1.el4_8.3

How reproducible:
curl -vL -H "Host: 20minutos.stats.com" http://77.67.41.161/liga/ 

Steps to Reproduce:
1. curl -vL -H "Host: 20minutos.stats.com" http://77.67.41.161/liga/
2.
3.
  
Actual results:
First response: < HTTP/1.1 302 Moved Temporarily
Second response: < HTTP/1.0 400 Bad Request


Expected results:
First response: < HTTP/1.1 302 Moved Temporarily
Second response: < HTTP/1.1 200 OK


Additional info:
On RHEL 5 with curl-7.15.5-9.el5, the result is always the expected.

Comment 1 Ondrej Vasik 2011-01-18 11:55:37 UTC

Thanks for report. We are sorry, but it's too late in RHEL-4 release cycle - at the moment we are addressing only critical and security related bugfixes in RHEL-4. Closing this bugzilla WONTFIX - as bugzilla is not a support tool - but bug tracking tool. 

If the issue is really critical for your business, please contact Red Hat Product Support - and inform them about this bugzilla.