[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Can anybody make any sense out of this? (it involves lack of DNS)
Hi James,
On 1/3/2012 7:35 PM, James Lampert wrote:
>> Any web requests going external from the<system name censored>
>> system go out through our Web applications Firewall ,
HTTPAPI supports via the http_setproxy() API
If authentication is required for the proxy ("web applications
firewall") then HTTPAPI supports BASIC authentication. (But not NTLM or
NTLMv2 at this time.)
> Can anybody here make any sense out of this? Or what it has to do with
> not having any DNS addresses set?
If you use a proxy, HTTPAPI always connects to the proxy, nowhere else,
and therefore the proxy is the only hostname HTTPAPI needs to resolve.
Any other hostname is resolved by the proxy itself (not by HTTPAPI) so
there'd be no need for local DNS resolution. (at least, as far as
HTTPAPI is concerned... )
> (My own response to this was that unless HTTPAPI at least *thinks* it's
> resolving the URL for the Google Calendar web services, in such a way
> that the requests and responses get through, it's "game over.")
I don't agree... but then, I don't know much about Google Calendar
services.
Anyway, if you want to try it, you'll want to put code like this into
your application, prior to doing any GET/POST with HTTPAPI:
http_setProxy( 'proxy.whatever.com': 8080 );
Where proxy.whatever.com is the name of the proxy server ("web
application firewall") and 8080 is the port number.
Or, with authentication:
http_setProxy( 'proxy.whatever.com': 8080 );
http_proxy_setAuth( HTTP_AUTH_BASIC
: 'the username'
: 'the password' );
Once that has been done, HTTPAPI will let the proxy handle the rest.
-SK
-----------------------------------------------------------------------
This is the FTPAPI mailing list. To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------