What did you see in the rule trace when reproducing this behavior?
If you have MCP installed as well as using MWG via proxy pac, the traffic you have bypassed in the proxy pac should be picked up by MCP (assuming its always redirecting).
If MCP is not "always redirecting" I would guess that the pages are not being sent to MWG and the content is blocked somehow.
Sorry for the delay in my answer, we were investigating this tricky issue with the support.
In a nutshell, we had two issues:
- Internet Explorer "compatibility mode" is activated for all sites (external and internal) when proxy pac file returns direct, because the pac file server is on the intranet it seems. This breaks many sites designs. See:
- MCP and the browser with a proxy pac file returning DIRECT cannot settle peacefully who is handling the socket. Basically we have to choose between (using MCP and no proxy) OR (no MCP and a pac file returning explicit proxies).
I hope this information will be helpful for people designing their solutions around MCP for intercepting traffic all the time (internally and externally): Think twice!