Response.Redirect Odditiy

  • Thread starter Thread starter Johnny Fugazzi
  • Start date Start date
J

Johnny Fugazzi

I have a couple of pages that have started showing an odd problem.

When the code calls Response.Redirect("file.aspx"), nothing happens. The
page goes white, and the old URL and querystring are displayed at the top of
the page. The page that was redirected towards does not come up.

Any ideas?
 
What, if anything, DOES come up?

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
What You Seek Is What You Get.
 
Here's an example..

Button is clicked, all of the code in the buttons Sub is executed and works,
and then it gets to a Response Redirect which would kick to the next page...

When it gets to this point it just seems to quit.

The page goes completely white, but the url and querystring remains. There
doesn't appear to be an error in my code, and no exceptions appear to be
thrown.

The same code works fine on my development box, but the problem occurs on my
server. Also has only started happening in the last day or two.

Just for kicks, I made a page with abutton that only does a
Response.Redirect(). Same thing happened.

I have restarted IIS and the server itself.
 
Are you adding the second optional parameter? Set it to false.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
What You Seek Is What You Get.
 
Hadn't been, but I just tried it and the result was that the page that
contained the button that triggered the action and the response.redirect was
reloaded.

when i changed the second parameter to true, i am back to the white screen
issue.

i have not been using a second parameter historically, and the white screen
issue just started happening in the last couple of days. I have not made
any changes that I know of that would cause odd behavior.
 
To add to the oddity, I did the following...

Created a new Virtual Directoryon the server, and published the project to
that spot.

Everything worked there.... So my question next is, is there a setting or
maybe something in the cache that I should clear out to make my primary
instance of the app work?
 
Hadn't been, but I just tried it and the result was that the page that
contained the button that triggered the action and the response.redirect
was reloaded.

when i changed the second parameter to true, i am back to the white screen
issue.
Click to expand...

True is the default. that was causing an unhandled exception. As to why the
particular page loaded, I would check your code.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
What You Seek Is What You Get.
 
To add to the oddity, I did the following...

Created a new Virtual Directoryon the server, and published the project to
that spot.

Everything worked there.... So my question next is, is there a setting or
maybe something in the cache that I should clear out to make my primary
instance of the app work?

The error handling I have going is not logging any errors at the point where
it stops working.
 
You mgiht try clearing your browser cache, but I don't know what the problem
is.

--
HTH,

Kevin Spencer
Microsoft MVP
..Net Developer
What You Seek Is What You Get.
 
JOhnyy,

Did you or anyone else figure out this problem. I am having what appears to
be the exact same problem,.

In my case, the app works perfectly well on my development machine (XP Pro),
but the response.redirect doesn't fire when I deploy it on a Windows 2003/IIS
6 server (I actually tried 2 different Windows 2003 IIS 6 systems and the
respoonse.redirect doesn't work on either one.

All of the code prior to the response.redirect is executing fine, no error
messages,.. It's just like the repsponse.redirect isn't there.
 
Back
Top