Brett Lymn <blymn@baesystems.com.au> had this to say,
> You can do this using a proxy.pac, if you want to make all https
> traffic direct then just match the start of the URL string for "https"
> and return "DIRECT" as the proxy method. If it is a single site that
> is causing the pain then just match that site. Be wary of making the
> proxy.pac too complex though, the thing gets evaluated on every URL
> lookup so it may affect browser performance if it is too unwieldy.
I don't want to send all https traffic DIRECT because I have
a virus filter through which request/responses go to after
the proxy and before the target.
I can workaround the problem by just matching the site, but
that doesn't solve the real problem, and before I release the
proxy to our entire Intranet usage, I need to understand what
is happening and fix that in order to prevent similar future
problems.
I just don't know where to go from here.
Help? Ideas? Anyone?
deb
-- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- There are 10 types of people in the world: those that understand binary, and those that don't. τΏτ ~Received on Fri Aug 09 2002 - 10:30:28 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:09:34 MST