From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.5) Gecko/20011012 Description of problem: Hi, I was attempting to do an ftp install via a proxy. The proxy is a username@host proxy, so you specify 'proxy' as the ftp host and 'ftp@server' as the username. During the RH7.2 install I used proxy as the server and selected non-anonymous and used ftp.org and dave as the password It succesffuly started the second part of the install and asked me about mice etc (I think) and then got to 'reading packages' and just sat there. Using alt-F2 I could see a repeated error scrolling up: IOError socket error occurred getting ftp://ftp@ftp.city-fan.org:%64%61%76%65@proxy/pub/redhat/enigma/i386/RedHat/base/hdlist Host not found So it looks like somewhere along the line there is a corruption of the name. Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.FTP install 2.Select non-anonymous 3. Additional info: i686 upgrading from RH7.0
We don't officially support FTP installs through proxy servers, so that's probably where the problem comes in. I would recommend downloading the ISOs and doing either a cdrom or a hard drive install. FTP installs without a proxy server works fine, though.
Given that there is nothing special used by the ftp proxy other than a special username then you do not actually have to have any special code to support an ftp proxy. The bug indicates a problem with either the non-anonymous ftp mechanism.
Non-anonymous FTP installs work for me without a proxy of any kind. I can't help but feel that the proxy is somehow causing this problem.
Do you think the problem could be the '@' in the username? ftp://ftp@ftp.city-fan.org:%64%61%76%65@proxy/pub/....... Do you think that something is parsing this as user: ftp.org password: dave host: proxy and something else is parsing it as: user: ftp password: ? host: ftp.city-fan.org:%64%61%76%65@proxy in which it would give the unknown host error. Just an idea, Dave
I don't know...could be.
I'm going to close this bug as "wontfix". If you see this behavior without having to go through a proxy server, please reopen this bug report. Thanks for your report.