Bug 683015 - libproxy fails with autoconfiguration "http://proxy.domain.com"
Summary: libproxy fails with autoconfiguration "http://proxy.domain.com"
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: libproxy
Version: 14
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Nicolas Chauvet (kwizart)
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-08 10:44 UTC by Martin Wilck
Modified: 2011-06-25 19:59 UTC (History)
4 users (show)

See Also:
Fixed In Version: libproxy-0.4.7-1.fc15
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-25 19:59:57 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
attached patch fixes the problem. (769 bytes, patch)
2011-03-08 10:44 UTC, Martin Wilck
no flags Details | Diff

Description Martin Wilck 2011-03-08 10:44:16 UTC
Created attachment 482869 [details]
attached patch fixes the problem.

Description of problem:
libproxy fails to get proxy with a Proxy Autoconfiguration URL with empty path, such as "http://proxy.domain.com". That's a valid URL and should be handled correctly.

Version-Release number of selected component (if applicable):
libproxy-0.4.4-7.fc14

How reproducible:
always

Steps to Reproduce:
1. Use libproxy with GNOME
2. Configure proxy autoconfiguration in GNOME, using an URL such as  "http://proxy.domain.com"
  
Actual results:
Proxy access fails because libproxy fails to retrieve the PAC (error 400 - illegal request), all apps relying on libproxy will fail to pass through the proxy.

Expected results:
Proxy access succeeds

Additional info:
See attached patch. The error is still in the latest upstream version. I sent an email to libproxy with the same patch today (Mar 8, 2011).

Comment 1 Martin Wilck 2011-03-31 08:20:23 UTC
Posting to the libproxy mailing list didn't work. I have filed an upstream bug now.

http://code.google.com/p/libproxy/issues/detail?id=159

Comment 2 Martin Wilck 2011-04-11 09:01:37 UTC
Patch was accepted upstream.

Updates:
	Status: Fixed

Comment #1 on issue 159 by dominiqu...: libproxy fails with  
autoconfiguration "http://proxy.domain.com"
http://code.google.com/p/libproxy/issues/detail?id=159

Thanks for the patch. Has been committed as r795.

Comment 3 Nicolas Chauvet (kwizart) 2011-04-12 09:37:17 UTC
Thx for the report.
I will backport it at least for f15.

Comment 4 Nicolas Chauvet (kwizart) 2011-04-13 10:28:23 UTC
Build for f15:
http://koji.fedoraproject.org/koji/buildinfo?buildID=238765

There is an ABI break involved so I cannot backport it for f14.
Here is a f14 scratch build at least:
http://koji.fedoraproject.org/koji/taskinfo?taskID=2997607

Comment 5 Fedora Update System 2011-05-05 09:32:31 UTC
libproxy-0.4.7-0.1svn20110412.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/libproxy-0.4.7-0.1svn20110412.fc15

Comment 6 Fedora Update System 2011-05-05 21:52:06 UTC
Package libproxy-0.4.7-0.1svn20110412.fc15:
* should fix your issue,
* was pushed to the Fedora 15 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing libproxy-0.4.7-0.1svn20110412.fc15'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/libproxy-0.4.7-0.1svn20110412.fc15
then log in and leave karma (feedback).

Comment 7 Fedora Update System 2011-06-09 08:02:55 UTC
libproxy-0.4.7-1.fc15 has been submitted as an update for Fedora 15.
https://admin.fedoraproject.org/updates/libproxy-0.4.7-1.fc15

Comment 8 Fedora Update System 2011-06-25 19:59:31 UTC
libproxy-0.4.7-1.fc15 has been pushed to the Fedora 15 stable repository.  If problems still persist, please make note of it in this bug report.


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