Recent Posts
Calendar
November 2013
S M T W T F S
« Oct    
 12
3456789
10111213141516
17181920212223
24252627282930

Posts Tagged ‘response’

DotNetNuke Response.End() Doesn’t End

screamOK.  This one is just plain annoying!

For some reason that I’ve yet to be able to track down, Response.End() seems to have no impact at all under DotNetNuke.

I tried various hacks.  Including the one you’ve probably seen already about executing Response.End() twice.  No good.

Execute Response.Close() and then Response.End() … infinite loop!

But I was able to come up with a solution that is reliable.

Read the rest of this entry »

Response.Redirect() and JavaScript

A toucan perched on a branch in Brazil. Yesterday we covered issues surrounding using Response.Redirect in server side code. We noted that not handing it correctly could prevent code from running on the server that we want to run.

The other issue is emitting Javascript in the server side in association with Response.Redirect(). This also leads to unexpected problems if you aren’t thinking about what is actually happening with your code.

Read the rest of this entry »

Response.Redirect() executes too soon on the Server.

tp_vol4_017 I’ve seen this question a couple of times in various situations. The first involves Javascript and the second involves server side code. Both are caused by a misunderstanding of what this function does and how web pages work.

Let’s start with the easy one: server side code.

Read the rest of this entry »