From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.4b) Gecko/20030523 Description of problem: When selecting HTTP install, and providing a site path of /~jacob/severn/ the Red Hat installer will request some files (the first such file is the hdlist) with the prefix //~jacob/severn/ which doesn't go to the same place. (I believe this to be a characteristic of the matching that mod_userdir does to know that it's supposed to head over to public_html.) Version-Release number of selected component (if applicable): Severn beta 1 installer. How reproducible: Always Steps to Reproduce: 1. Set up an install under a userdir (~msw/public_html) 2. Select HTTP install 3. Wait for it to tell you that it can't load the header list 4. Inspect your HTTP logs to see the extra leading / 5. (Optional) add a RedirectMatch rule so that you can install anyway
Severn beta1 bugs are supposed to be marked i386, I now recall.
*** Bug 101522 has been marked as a duplicate of this bug. ***
I think I have this fixed. Please try again in our next beta.
*** Bug 123607 has been marked as a duplicate of this bug. ***
I've downloaded anaconda-10.0-5.src.rpm and tried to trace the logMessages. In mountUrlImage() in loader2/urlinstall.c, we start in the URL_STAGE_MAIN state and call urlMainSetupPanel() in loader2/urls.c. This function gets the URL from the user and stores it in a (struct iurlinfo). It also forces ui->prefix to have a leading slash. Returning to mountUrlImage(), we change to the URL_STAGE_FETCH state and call loadUrlImages(), which calls loadSingleUrlImage(), which calls urlinstStartTransfer() in loader2/urls.c. This function generates the "transferring http://..." logMessage with the extra slash I see in virtual terminal 3. The bad URL is then passed to httpGetFileDesc() in loader2/ftp.c, which presumably fails. There is a block near the end of mountUrlImage() with the comment "sanitize url so we dont have problems like bug #101265" "basically avoid duplicate /'s" but I think this bug occurs before it is reached.
Mass-closing lots of old bugs which are in MODIFIED (and thus presumed to be fixed). If any of these are still a problem, please reopen or file a new bug against the release which they're occurring in so they can be properly tracked.