[EMAIL PROTECTED] wrote:
It looks like my lynx does not understand the response from proxy.
The response is from something which isn't yet the proxy. The best
way of getting rid of it is make it the proxy!
Content-Type: application/x-ns-proxy-autoconfig
This is a Netscape proprietary extension (x-ns), although may
well be recognized by recent IEs.
// Client IP address: 10.1.2.3
function FindProxyForURL(url, host) {
This is EcmaScript; Lynx doesn't support scripting.
How can I configure Lynx to understand the proxy response ?
It isn't a proxy response. A proxy would respond with the
requested page. It's a response you are getting because you
aren't using the (right) proxy, but the proxy has intercepted the
request.
Write an EcmaScript interpreter and enough of the Netscape browser
object model to support this application. Of examine the script
returned for all the platforms that you are interested in, and write
ad hoc code to pick the relevant parameters from the script. Or,
simply manually configure the correct proxy.
Note Lynx can only support one proxy, so, if the script selects
different proxies for different destinations, you will have to implement
a proper or hack interpreter for the script.
--
David Woolley
Emails are not formal business letters, whatever businesses may want.
RFC1855 says there should be an address here, but, in a world of spam,
that is no longer good advice, as archive address hiding may not work.
_______________________________________________
Lynx-dev mailing list
[email protected]
http://lists.nongnu.org/mailman/listinfo/lynx-dev
