I'm wondering if anyone else has had issues with BorderManager not
liking
pages that have the URI information stripped out. Here's what happens
on
our network.

We use our BorderManager server for caching and user logging. It then
goes
through a WatchGuard Firebox, which runs an HTTP proxy service, which
does
our filtering, and this watchguard service is transparent. Our
problem is
that the WatchGuard software strips out certain header information
regarding
Uniform Resource Locator information, and when accessing a web page
through
our proxy server, we get 400 - Bad Request errors. Take out the
border
manager proxy setting in the browser and everything works fine.
WatchGuard
says that this is something that can't be changed, which I personally
think
is poor software design on their behalf, as they don't give many
options to
tweak their proxy settings.

Are there any hidden BM settings to try? We are running BM 3.7. Anysuggestions?

Thanks,

Ryan