Welcome to ISAserver.org

Serious http proxy problems...

Users viewing this topic: none

Logged in as: Guest

Printable Version

All Forums >> [ISA Server 2004 Firewall] >> HTTP Filtering >> Serious http proxy problems...

Page: [1]

Message

<< Older Topic Newer Topic >>

Serious http proxy problems... - 21.Mar.2005 5:13:00 PM

adam_nerell

Posts: 5
Joined: 7.Mar.2005
Status: offline

I've got an ISA2004 running, no strange configs at all and a 2mbit connection. However certain sites will not load properly with my ISA server e.g. www.neowin.net, www.gmail.com after logging in it takes more than 5 minutes to actually get to the Gmail gui, if it works at all.

If I bypass the isa all together it works fine. There isn't any droped packet or other strange behaviour that could explan this..

Is there any tweaks or problems one should be aware of?

Post #: 1

Featured Links*

RE: Serious http proxy problems... - 24.Mar.2005 2:14:00 AM

WyldWolf

Posts: 246
Joined: 3.Mar.2005
From: Wisconsin
Status: offline

Is your ISA behind another filtering device or router?

No issues with either of these sites, just tested and got response through my ISA in seconds.

(in reply to adam_nerell)

Post #: 2

RE: Serious http proxy problems... - 22.Apr.2005 1:28:00 AM

Guest

I have been experimenting the same situation with gmail.com

(in reply to adam_nerell)

Post #: 3

RE: Serious http proxy problems... - 22.Apr.2005 6:09:00 PM

berlamont

Posts: 1
Joined: 22.Apr.2005
Status: offline

Hey this is my first post but I happen to come across this question through google. My company is having the same problems and we found this link which may be helpful.
ISA Connection problems with some sites.

(in reply to adam_nerell)

Post #: 4

RE: Serious http proxy problems... - 23.Apr.2005 2:58:00 AM

LoginKat

Posts: 12
Joined: 18.Jul.2002
Status: offline

I have a client who has been experiencing similar difficulties with ISA 2004 since SP1. In at least once instance I was able to see that the HTTP filter was mangling the URL of the destination site because it contained a "%". For example:

http://dummydomain.xxx/somepage?Container=com.xyzzy.entity.Entity%5BOID%5B62D62A9C2531774FA27F21D0926E8C97%5D%5D

becomes:

http://dummydomain.xxx/somepage?Container=com.xyzzy.entity.Entity%255BOID%5B62D62A9C2531774FA27F21D0926E8C97%255D%255D

Note that all instances of "%" have been escaped as "%25" rendering the urls data useless.

In my case I was able to create an http access rule for just the two vendor sites the client was having issues with that was unbound from the http application filter. This seemed to fix their problem. But this is just a workaround - it seems as though the http application filter is a bit too aggressive in its normalization.

(in reply to adam_nerell)

Post #: 5