Bug 230242

Summary:	passing ks=http://192.168.1.1/foo/bar/ results in GET /./foo/bar
Product:	Red Hat Enterprise Linux 4	Reporter:	John Franklin <jfranklin>
Component:	anaconda	Assignee:	Chris Lumens <clumens>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	medium	Docs Contact:
Priority:	medium
Version:	4.4
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	RHEL5	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2007-04-20 14:33:32 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 John Franklin 2007-02-27 18:18:13 UTC

Description of problem:
Passing in an http URL for a kickstart config file results in a get with a /.
(slash-dot) prepended to the path.  This confuses some fastcgi services like Rails.

Version-Release number of selected component (if applicable):
KS boot environment is as shipped on the 4u4 CDs
Ruby 1.8.5
Rails 1.1.6
ruby-fcgi 0.8.7
Apache 2.2.2

How reproducible:
100%

Steps to Reproduce:
1. Set up a Ruby on Rails environment
2. Boot with ks=http://<bootServerIP>/<some path that maps to RoR>
3. Observe in access_log "GET /./<some path>" returning a 404.
  
Actual results:
192.168.100.229 - - [27/Feb/2007:10:05:24 -0800] "GET /./systems/kickstart/2
HTTP/1.0" 404 610

Expected results:
192.168.100.229 - - [27/Feb/2007:10:05:24 -0800] "GET /systems/kickstart/2
HTTP/1.1" 200 5588

Additional info:

Comment 1 Chris Lumens 2007-04-04 14:15:26 UTC

Is this better in RHEL5?  I did some work on sanitizing these strings in the FC6
timeframe, so it should be a little better in that release.

Comment 2 John Franklin 2007-04-19 22:07:07 UTC

Yes, better.  A RHEL5 run reports:

192.168.100.229 - - [19/Apr/2007:15:05:28 -0700] "GET /systems/kickstart/8
HTTP/1.0" 200 7032

Comment 3 Chris Lumens 2007-04-20 14:33:32 UTC

Okay, then I'm going to close this out as CURRENTRELEASE.  If you require this
fix to be backported for a RHEL5 update release, please speak with your support
representative who will raise it through the appropriate channels.  Thanks for
the bug report and the testing.