I was wondering if someone could explain to me why the DNN base code always uses EndResponse = True when  doing a redirect?

I can understand that this is necessary sometimes but it seems to be used regardless of whether it's necessary?  

I find this unusual because as far as I know this the opposite of Microsoft's recommended approach.
"we recommend that instead of this overload you use the HttpResponse.Redirect(String, Boolean) overload and pass false for the endResponse parameter, and then call the CompleteRequest method."  -> http://msdn.microsoft.com/en-us/libra...

The reason I'm asking is because the DNN site I took over maintanace for has EndResponse = True all over the place (copied from DNN core code example I'm sure) and it seems to cause the session info to sporadically disappear when running in DNN 5.5/.NET4.0.

Before I switch the custom code I thought I'd try to get some more information on why the base DNN code is using this pattern?

Thanks in advance for any insight you can give.

Tommy

Thanks Will for the info:

'This is because more often than not, the overload allows us to prevent errors that spawn from multi-threading'

However, I am not aware of a general issue involving Redirects and Multi-threading, and I just Googled it and didn't find anything, can you elaborate a bit more please? 


Thanks again,