I have a mix of asp.net and asp classic pages in the same application. Could any tell how do I do a response.redirect to the asp classic pages? I get a error using the normal way.
View Complete Post
Hi. I'm using the Dundas Chart Controls in VS 2005. These controls are built utilizing AJAX. I have a basic page with a dundas chart control containing a funnel chart. The funnel contains Quotes, Sales Orders and Invoices. When the user clicks on the control, I want to determine whether they clicked on Quotes, Sales Orders or Invoices and transfer to the appropriate Details Page. I've got the code working to determine which transaction type they clicked on; but, I get the "Response.Redirect cannot be called in a page callback." error when the page tries to redirect. Note: I get a similar issue if I try server.transfer.
Here's my code:
Dim hitTestResult As Dundas.Charting.WebControl.HitTestResult = Chart1.HitTest(e.X, e.Y)
If Not (hitTestResult Is Nothing) Then
Dim clicked As Dundas.Charting.WebControl.DataPoint = hitTestResult.Series.Points(hitTestResult.PointIndex)
Select Case hitTestResult.PointIndex
I am using some code similar to the code below to open a word document on my ASP.net app. Once the file has been downloaded and opened I then want to either redirect to another page or refresh the screen but nothing works after response.end and if i add it before response.end the browser never downloads the file?
Response.AddHeader("Content-Disposition", "attachment; filename=" + file.Name
Response.ContentType = "application/octet-stream";
Any ideas? Thanks
I'm in the middle of migrating servers and on the new server Response.Redirect is extremely slow. It takes around 20 seconds for the browser to get the redirect. This is something that was quick on the existing server. It's an ASP.NET 2.0 application, both servers are running IIS6.
Additionally, if I "manually" do the redirect, it's fast. For example:
takes around 20 seconds on the new server
Response.Status = "302 Moved Temporarily";Response.AddHeader("Location", url);Response.End();
is fast on the new server.
Any ideas why Response.Redirect would be so slow on the new server?
I need to open a new window with Response.Redirect, Is it possible?
Hello, I will try to be as clear as I can be. I'm sure this question has been asked but I can't find a suitable answer for this particular situation.
I need to be able to redirect the browser to a new 3rd party page while at the same time supplying a cookie required for some form of authentication on the 3rd party site.
I have managed to get this to work in the following manner:
'SessionID is predetermined by another HttpWebRequest/Response
Dim sessionCookie As New Cookie("ezproxy", sessionID.Substring(1), "/", ".someother.site")
Dim CookieJar As New CookieContainer
rRequest = HttpWebRequest.Create("where I want to go")
rRequest.CookieContainer = CookieJar
rRequest.Method = "GET"
'Make the request and get the response.
rResponse = rRequest.GetResponse()
If (rResponse.Cookies.Count <> 0) Then
For Each cook