Bug 47039 - HTTP TUI install isn't prepending / to "Red Hat directory"
Summary: HTTP TUI install isn't prepending / to "Red Hat directory"
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.3
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Matt Wilson
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2001-07-02 19:01 UTC by Brent Nordquist
Modified: 2007-04-18 16:34 UTC (History)
0 users

(edit)
Clone Of:
(edit)
Last Closed: 2001-07-02 20:23:58 UTC


Attachments (Terms of Use)

Description Brent Nordquist 2001-07-02 19:01:05 UTC
Description of Problem:
When doing HTTP TUI install of Fairfax beta1, got an error retrieving
stage1 because the HTTP request didn't have a leading / on the URI.  Adding
"/" to the front of the TUI field fixes it.  There is also a typo on one of
the HTTP TUI dialogs.

How Reproducible:
Consistently.

Steps to Reproduce:
1. Answer questions about language and keyboard type.
2. For [Installation Method] dialog, choose HTTP.
3. For [Configure TCP/IP] dialog, choose:
   [ ] Use dynamic...
       IP address:            172.18.34.16
       Netmask:               255.255.192.0
       Default gateway (IP):  172.18.1.15
       Primary nameserver:    172.18.14.1
4. For [HTTP Setup] dialog, choose:
   Web site name:      172.18.1.28
   Red Hat directory:  fairfax/beta1/i386

Actual Results:
Received dialog [Error] with text:
Failed to retrieve fairfax/beta1/i386/RedHat/base/netstg1.img: Bad FTP
server response.
(a) Note the error says "FTP", should be "HTTP".
(b) Inspecting the Apache access_log finds:
Invalid URI in request GET fairfax/beta1/i386/RedHat/base/netstg1.img HTTP/1.1
(note no leading slash on the path)

Expected Results:
can be had by changing "Red Hat directory" to "/fairfax/beta1/i386" but
many people will probably trip over this.

Comment 1 Matt Wilson 2001-07-02 20:23:54 UTC
should be fixed in CVS, needs testing.
47039


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