certi-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [certi-dev] CERTI billard test / http_proxy


From: Martin Spott
Subject: Re: [certi-dev] CERTI billard test / http_proxy
Date: Tue, 19 May 2009 12:46:30 +0000 (UTC)
User-agent: tin/1.9.2-20061221 ("Benmore") (UNIX) (SunOS/5.10 (sun4u))

Martin Spott wrote:

> From this comment, I understand that I should set $CERTI_HTTP_PROXY to
> None (probably also lower-case none !?) to disable the use of a proxy
> even if $http_proxy is set. Right ?

Ah, from ./libCERTI/SocketHTTPProxy.cc:

"To disable HTTP tunneling, you must unset both environment variables,
or set CERTI_HTTP_PROXY to an empty string."

Here we go:

quickstep: ~> echo $http_proxy
http://proxy.<domainname>:3128/
quickstep: ~> setenv CERTI_HTTP_PROXY ""
quickstep: ~> billard -fTest -FTest.fed -n 1
CERTI Billard 3.3.3cvs
with TIMESTAMP. If you want without TIMESTAMP add -e option.
RTIA:: RTIA has thrown NetworkError exception.
RTIA:: Reason: gethostbyname gave NULL answer for hostname <> with error 
<Unknown error: 0>
RTIA:: End execution.


As far as I understand, line 111/112 in ./libCERTI/SocketHTTPProxy.cc
don't properly tell the difference between "variable unset" and
"varable set, but empty", because getenv("CERTI_HTTP_PROXY") returns
NULL even for an empty variable (note: just guessing). Am I wrong here ?

Cheers,
        Martin.
-- 
 Unix _IS_ user friendly - it's just selective about who its friends are !
--------------------------------------------------------------------------




reply via email to

[Prev in Thread] Current Thread [Next in Thread]