Hi Chris, You're right, it's a very old version of Squid but upgrading is not option yet... However you were spot on with your suggestion. I just added the line: extension_methods SEARCH (after searching the firewall's log for the unsupported method) To the configuration file and it worked. Thanks. -----Original Message----- From: Chris Robertson [mailto:crobertson@xxxxxxx] Sent: Monday, October 24, 2005 2:36 PM To: squid-users@xxxxxxxxxxxxxxx Subject: RE: OWA contents frame displays "Loading" Two things... > Hello to all, > > First the setup of my Internet connection: > > Internet ←→ SEF Firewall ←→ Proxy (RH 7.2 Squid 2.4STABLE7) ←→ > Clients > This is a very old version of Squid (and RedHat). You might find that a newer version works better. > Now the problem: When users try to connect with an external OWA > server, they get a Web page appearing with all the information except > the actual emails. Instead, it displays "Loading...." in that part of > the Web browser. According to Microsoft > (http://support.microsoft.com/?kbid=280823) there are several reasons > for this behavior, but as the connection works just fine when the > client connects directly to the Internet I thought that the first > reason was the most likely: > > "Internet Explorer version 5.0 and later supports HTTP-DAV as > described in Request for Comments (RFC) 2518). Distributed Authoring > Version (DAV) uses Hypertext Transfer Protocol (HTTP) verbs that your > proxy server or firewall does not recognize. Additionally, your proxy > or firewall solution does not permit you to customize the list of > approved HTTP verbs." > > So I began troubleshooting this problem by checking the Symantec KB > where I found an entry referring to this specific problem so I > followed to the letter the article but to no avail. However I tested > the connection bypassing the proxy and connecting directly to the > firewall and it worked so it seems that the problem lies now in the > proxy side. > > I checked the mail archive but the only thing I found was to use the > always_direct directive which for me is not an option because my > default gateway points to the intranet and there is no chance of > adding a static route pointing to the Internet. ¿Any suggestions? > The always_direct statement only has bearing when using a hierarchy (parent and/or sibling caches). It wouldn't solve your problem here. If you are unwilling or unable to upgrade, check the access.log for clues as to what is going on. http://www.webdav.org/other/proxy.html states that you might need to look into the "extension_methods" directives for Squid 2.4. Your squid.conf should have more information on how to use it. > Thanks for your help. Chris
