This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Behavior Chrome vs IE with Web Appliance

Good morning
I'm having a pretty weird situation. I'm using Sophos web appliance in Explicit mode with the use of the .dat file. In the .dat file all internal networks have been excluded but when I point to an internal IP address with Internet Explorer it cannot display it correctly, while with Chrome the display is correct. By removing the proxy the site is correctly displayed. I tried to see all the security settings of IE I checked the configuration of the .dat file, the link to the internal site is direct. I don't understand how proxy configuration can affect an internal site and above all because it works with Chrome. What are the differences?
Thanks for any help
Best regards
Franco



This thread was automatically locked due to age.
Parents
  • Hi 

    thank you very much for the answer, we are testing again with new information. One thing we are noticing is that the site should work with Microsoft Silverlight. What do you know there are compatibility problems between the .dat or .pac file with Silverlight?

    Thank you very much for all information

    Best regards 

    Franco

  • Not much of a ms guy .. but from what I recall SL Is enforced at a lower level then the application.. ie if you have “use automatic settings “ checked off (even of you specify a proxy).. you get cases where ie will applythe automatic setting before the proxy settings where as chrome and ff enforce proxy first..

    Also make sure forward and revers dns works for the appliance both short and long name...as well ensure the appliance is listed in the zones configuration in ie

Reply
  • Not much of a ms guy .. but from what I recall SL Is enforced at a lower level then the application.. ie if you have “use automatic settings “ checked off (even of you specify a proxy).. you get cases where ie will applythe automatic setting before the proxy settings where as chrome and ff enforce proxy first..

    Also make sure forward and revers dns works for the appliance both short and long name...as well ensure the appliance is listed in the zones configuration in ie

Children
No Data