Home
Reading
Searching
Subscribe
Sponsors
Statistics
Posting
Contact
Spam
Lists
Links
About
Hosting
Filtering
Features Download
Marketing
Archives
FAQ
Blog
 
Gmane
From: Steffen Moeller <steffen_moeller <at> gmx.de>
Subject: Bug#524127: [uscan] 'x509_user' not valid URI scheme at /usr/bin/uscan line 389
Newsgroups: gmane.linux.debian.devel.bugs.rc
Date: Thursday 16th April 2009 12:26:27 UTC (over 7 years ago)
Hi Adam,

Adam D. Barratt wrote:
> On Thu, 2009-04-16 at 02:45 +0200, Steffen Moeller wrote:
>> the issue seems to be invariant of the watch file used. It still occurs.
> [...]
>> $ set | grep -i proxy
>> X509_USER_PROXY=/home/moeller/myproxy
> 
> Aha! This seems to be due to a change made upstream in libwww-perl in
> version 5.821:
> 
>       croak on bad proxy args [RT#39919]
> 
> This is easily confirmable by checking whether the following also fails
> for you:
> 
>         #! /usr/bin/perl
>         use LWP::UserAgent;
>         my $ua = LWP::UserAgent->new(env_proxy => 1);
>         
> env_proxy is documented as reading environment variables of the form
> *_proxy.

Your hunch did not fool you.

$ perl a.pl
'x509_user' is not a valid URI scheme at a.pl line 3

It (including uscan) works with env_proxy => 0, but this obviously is not
what you want.

> LWP maintainers - any thoughts? Should clients (e.g. uscan) be
> attempting to sanitise the proxy variables in the environment to only
> include those they specifically care about before using env_proxy? (or
> wrapping the call in an eval() and ignoring the specific error)
> 
> That's obviously doable, but would need doing in every client
> individually, which seems somewhat overkill.

Somehow it seems strange to reserve all _PROXY variably for oneself.

Best,

Steffen
 
CD: 3ms