"ArunTam" <ArunTam@discussions.microsoft.com> wrote in message news:10A0726B-866E-45E5-8924-C44A651BBF4D@microsoft.com...
> I am trying to redirect users using HTTP/1.1 307 temporary redirect. But I
> have found that while sometimes the redirect works, at other times it doesnt.
> We have done some troubleshooting, and would appreciate your helping us
> understand why this could be happening and also how to fix this.
> Troubleshooting that we have done so far:
> - Under Tools, Advanced, have "Restored Advanced settings" to default and it
> has worked sometimes, but not at all times
> - Have taken a wireshark capture and have found that the Redirect is
> received by the laptop but DNS query for the new destination does not occur.
That wouldn't necessarily imply a problem. E.g. the lookup might be found
in the dnscache. Supposedly there is also a separate lookup cache that
IE maintains for up to 30 minutes (by default, ref. KB263558)
<TITLE>How Internet Explorer uses the cache for DNS host entries</TITLE>
(Support site search for
dns timeout default "internet explorer"
In order to eliminate those factors from consideration you would have to
do things such as ipconfig /flushdns and close all instances of iexplore.exe
before each test. <eg>
Then, if the page was cached, your cache-checking options would take over
and if that was anything other than Every time... you might not even see a request
made. ; )
> - Typing the new destination's url is IE7 by itself works though the
> redirect does not.
> - The redirect works without a problem with IE6.
> I can share the wireshark capture with you. Looking forward to getting more
> insight on this issue! Your help in this is greatly appreciated!!
I would try using ProcMon (or FileMon) to see what is happening
with the TIF. Also, have you tried using Fiddler2? That would be slightly
different since it would be going through a proxy but it would be simpler
to see if (for example) there is a problem with accumulated missing responses
from the host.
Have you tried IE8 to see if it changes your symptoms? The previous comment
just reminded me that it has supposedly changed the default MaxConnectionsPer1_0Server
for broadband users. Or just use try a registry hack (Ref. KB282402)...
<TITLE>How to configure Internet Explorer to have more than two download sessions</TITLE>
If this resolves the problem you may have more proof of its cause
by using netstat (in a cmd window). E.g. netstat -ap tcp
Heh. That just reminded me that I once saw a related problem apparently caused
by a user's AV package when it was configured to monitor all HTTP sessions.
So. if you already have a proxy IE could be issuing the request but the proxy
might be blocked from forwarding it. I'm not sure if WireShark would capture
such an intermediate request, e.g. via the TCP loopback, especially if you are only
having it trace the real network interface. ; )