asp.net: response.redirect not working

Question

I have a .aspx form in which I have a combobox holding subject I retrive from a DB-table.

A submit button clicking on which questions related to that subject are viewed in a gridview.

I do it by calling the function FillGrid() in the button click event.

I also have pageindexchanging for my gridview in which FillGrid() is again called.

In my FillGrid() function I have used a try catch block. If an error occurs I want to redirect the page to error page using Response.Redirect(). The problem is this response.redirect is not working. One of the reasons of it is that on button click the form is posted twice. Because after reaching to response.redirect statement flow comes back to button click where FillGrid is called().

How can I solve this? Or to put simply, how can I prevent double posting of the form?

Is this triggered by a control inside an UpdatePanel?

Jeff Sternal
– Jeff Sternal

2009-11-30 16:04:06 +00:00
Commented Nov 30, 2009 at 16:04 — Jeff Sternal
– Jeff Sternal, Commented Nov 30, 2009 at 16:04
no i m not using Updatepanel...

anay
– anay

2009-11-30 16:06:49 +00:00
Commented Nov 30, 2009 at 16:06 — anay
– anay, Commented Nov 30, 2009 at 16:06

Sicco · Accepted Answer · 2012-09-16 14:23:28Z

8

For example you need to link index.aspx. So you write this:

Response.Redirect("index.aspx", true);

But Response.redirect is not working. Now go to design view select the button which you want to set Response.redirect and press F4 that will open Button Properties then you need to find PostBackUrl option and then locate your URL that you want.

See this image:

edited Sep 16, 2012 at 14:23

Sicco

6,3295 gold badges49 silver badges63 bronze badges

answered Sep 16, 2012 at 6:46

Samir Rajak

811 silver badge2 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Vibhum Bhardwaj · Accepted Answer · 2015-07-13 19:51:37Z

3

Well, do this...

Response.Redirect("~/err.aspx", false);
HttpContext.Current.ApplicationInstance.CompleteRequest();

Now the original page won't be posted back to the browser and you will be redirected to the new page.. The problem with Response.Redirect("~/err.aspx", true); is that an exception is formed that way, which may send the control to the catch block..

•Another way is of course Server.Transfer() but I don't think you wanted that.

answered Jul 13, 2015 at 19:51

Vibhum Bhardwaj

928 bronze badges

Comments

Ahmet Arslan · Accepted Answer · 2013-04-25 08:39:59Z

2

I have encountered exactly same problem. Redirect was not working because of content page's master page has errors. This is sample code:

FormsAuthentication.SetAuthCookie(loginUserDetail.UserName, false);
Response.Redirect(FormsAuthentication.DefaultUrl, false);

FormsAuthentication.DefaultUrl value is "/membersarea/wellcome.aspx" and wellcome.aspx has a master page named, Site.master.

Site.master had javascript errors, so Response.Redirect command was not working.

edited Apr 25, 2013 at 8:39

answered Apr 19, 2013 at 13:51

Ahmet Arslan

6,2803 gold badges36 silver badges38 bronze badges

Comments

Oded · Accepted Answer · 2009-11-30 15:40:13Z

1

Try this:

Response.Redirect("url");
Response.End;

answered Nov 30, 2009 at 15:40

Oded

501k102 gold badges900 silver badges1k bronze badges

2 Comments

Jeff Sternal Over a year ago

That's the default behavior for Response.Redirect.

Marc Over a year ago

Response.Redirect("url", true) is saying the same thing.

Jeff S · Accepted Answer · 2009-11-30 16:18:50Z

0

I believe the behavior you are seeing is correct. A response.redirect is done through the browser. So when you get an error, the page is posted to the browser and the browser triggers the redirect. The redirect causes the page_load to fire again (this is the standard flow in ASP.NET).

While you can use Server.Transfer to get around this, I'd recommend using the error redirection built into ASP.NET. See this page for more information on what's available and how to use them.

answered Nov 30, 2009 at 16:18

Jeff S

7,49432 silver badges32 bronze badges

Comments

Steve · Accepted Answer · 2020-03-09 18:53:39Z

0

For me, the re-direct issue was with my web.config file. In that file, each page was specifically allowed access. Once I added the code block for my new page I was re-directing to in the web.config file the re-direct worked. Hopefully, if someone has a similar issue it can save them time and not waste most of a day like I did.

In web.config file I added a code block like below:

  <location path="sitedirectory/yournewpage.aspx">
    <system.web>
      <authorization>
        <allow users="*"/>
      </authorization>
    </system.web>
  </location>

answered Mar 9, 2020 at 18:53

Steve

11 bronze badge

2 Comments

Jeremy Caney Over a year ago

Hello, @Steve, and welcome to Stack Overflow. This is definitely a valid solution to the problem where an automatic redirect doesn't occur when an unauthenticated user accesses a page. That said, the original question is about an explicit Response.Redirect() and doesn't pertain to the framework's built in authentication scheme. Instead, they were dealing with issues related to web forms event model.

Steve Over a year ago

Thanks. I realize that my solution wasn't specifically addressing the OP's issue but since I ended up here looking for a solution to related Response.Redirect problem I thought that others may too. I'll try to be more cognizant of addressing the OP's specific issue for the future.

FloverOwe · Accepted Answer · 2023-11-15 00:37:00Z

0

When all else fails with server-side coding, you can try JavaScript, such as location.href=someUrl; or location.replace(someUrl);. Have some server-side code that sets a JavaScript flag to trigger the JavaScript, or conditionally generate needed JavaScript. I usually have the triggered JavaScript at the bottom of the web page.

answered Nov 15, 2023 at 0:37

FloverOwe

3732 silver badges12 bronze badges

Collectives™ on Stack Overflow

asp.net: response.redirect not working

7 Answers 7

Comments

Comments

Comments

2 Comments

Comments

2 Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

7 Answers 7

Comments

Comments

Comments

2 Comments

Comments

2 Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related