as you know it is possible to generate the PAC-File dynamically using the MWG.
We use this for a while.
HTTP support GZIP encoding.
HTTP: GET /proxy.pac HTTP/1.1
HTTP: cache-control: no-cache
HTTP: connection: keep-alive
HTTP: pragma: no-cache
HTTP: dnt: 1
>>>HTTP: accept-encoding: gzip,deflate<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
HTTP: accept-language: en-US,en;q=0.5
HTTP: user-agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0)Gecko/20100101 Firefox/17.0
HTTP: host: xxxxxxxxx.xxxx
Currently MWG does not zip our answer.
Is it possible to build a rule that supports gzip encoding?
This will help us to reduce the PAC-File size (currenty 6,7K)
It is not possible to build a rule to gzip the data. :-/ (https://community.mcafee.com/message/202364#202364)
If transaction goes through the MWG rule engine it will follow that process (not compressed on client side).
It may be possible using the file server, but I have not tested it.
If you use the file server, it still needs to process through the proxy to replace the body content dynamically, and even if it gzipped from localhost to the proxy, it would still be uncompressed from the proxy to the client
isn't the proxy.pac file cached on the clients and only transferred every now and then? So I would expect the Proxy.Pac to not cause a lot of traffic.
we diskussed this feature last week at the inner circle meeting in Unterschleissheim/Munich. There is a way to generate a PAC File dynamic using some nice features like Body.ToFile Event and so on. :-)