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

[Martin Spott]

Hi Petr,

"Gotthard, Petr" wrote:

> We understood $http_proxy as a global variable that should affect all
> applications, including CERTI. The $CERTI_HTTP_PROXY is meant to change
> the global behavior, i.e. enable proxy if $http_proxy is not set, or
> disable proxy if $http_proxy is set.
> https://savannah.nongnu.org/patch/?func=detailitem&item_id=6561#comment1

>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 ?
As far as I can tell, this doesn't work properly:

quickstep: ~> billard -fTest -FTest.fed -n1
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 <None> with error 
<Unknown error: 0>
RTIA:: End execution.
libRTI: exception: NetworkError (read)


....  while:

quickstep: ~> unsetenv http_proxy
quickstep: ~> billard -fTest -FTest.fed -n1
[...]


works nicely (note that $CERTI_HTTP_PROXY has to be unset as well).

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