views:

469

answers:

2

Why does using Fiddler break my site sometimes on page transitions.

After a server side redirect -- in the http response (as found in Fiddler) I get this:

Object moved

Object moved to here.

The site is an ASP.NET 1.1 / VB.NET 1.1 [sic] site.

Why doesnt Fiddler just go there for me? i dont get it.

I'm fine with this issue when developing but I'm worried that other proxy servers might cause this issue for 'real customers'. Im not even clear exactly what is going on.

+2  A: 

That's actually what Response.Redirect does. It sends a 302 - Object moved response to the user-agent. The user-agent then automatically goes to the URL specified in the 302 response. If you need a real server-side redirect without round-tripping to the client, try Server.Transfer.

yes, but why does Fiddler just stop dead? shouldnt it send me there?is this just Fiddler's behavior or am i liekly to run into this problem with any other type of Proxy?
Simon_Weaver
I am using Fiddler 2.1.0.4 and I am not seeing the behavior you described. It follows the redirects for me just fine. As long as Fiddler forwards the 302 to the browser, the browser should request the new URL and this will show up in Fiddler. Fiddler by itself won't follow the redirect.
Fiddler shouldn't "send" you anywhere, your client is responsible for requesting the information from the new URL. However, Fiddler might have rewritten the information in a way your client doesn't understand. Perhaps you can post the _exact_ raw response, and info about your particular client?
Paul-Jan
+1  A: 

If you merely constructed the request using the request builder, you're not going to see Fiddler automatically follow the returned redirect.

In contrast, if you are using IE or another browser, it will generally check the redirect header and follow it.

For IE specifically, I believe there's a timing corner case where the browser will fail to follow the redirect in obscure situations. You can often fix this by clicking Tools / Fiddler Options, and enabling both the "Server" and "Client" socket reuse settings.