Bug 328121 - yum needs trailing slash on proxy port number
Summary: yum needs trailing slash on proxy port number
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: yum
Version: 7
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2007-10-11 18:46 UTC by Michael Rice
Modified: 2014-01-21 22:59 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2008-03-13 15:16:32 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
non-working yum.conf (306 bytes, text/plain)
2007-10-12 19:35 UTC, Michael Rice
no flags Details

Description Michael Rice 2007-10-11 18:46:51 UTC
Description of problem:
To get yum to use a proxy you must add a trailing slash to the port


Version-Release number of selected component (if applicable):
yum-3.2.5-1.fc7

How reproducible:
every time


Steps to Reproduce:
1.set proxy=http://some.proxy:3128 in yum.conf
2.
3.
  
Actual results:
[Errno 4] IOError: <urlopen error nonnumeric port: '3128?'>



Expected results:
it should work


Additional info:
to fix it add :3128/

Comment 1 Jeremy Katz 2007-10-11 20:35:27 UTC
It looks like there's a non-printable character that snuck in there.  Can you
attach your entire yum.conf in its non-working state? 

Comment 2 Michael Rice 2007-10-12 19:35:49 UTC
Created attachment 226041 [details]
non-working yum.conf

Comment 3 Michael Rice 2007-10-12 19:38:10 UTC
I used od -c on the file and \n is the only thing to follow :3128

0000260   m   :   3   1   2   8  \n



Comment 4 Dave Russell 2007-10-23 15:14:42 UTC
I had the same issue, but I think the "non numeric port" might be a red herring.

For me if I use the documented:
proxy=
proxy_user=
proxy_pass=

Then it breaks...

However if I use:

proxy=http://proxy_user:proxy_pass@proxy.url

Then it works!

Give that a try.

Comment 5 Seth Vidal 2008-03-12 14:54:47 UTC
YUMBUGDAY

Comment 6 James Antill 2008-03-13 15:16:32 UTC
 Ok, I see the problem ... fixed.



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