Endless loop when calling an HttpHandler?

By this I mean try to evaluate either the Referrer or UserAgent and see who's making the request I wonder if the flash app you're instantiating might somehow be the issue here.

By this I mean try to evaluate either the Referrer or UserAgent and see who's making the request. I wonder if the flash app you're instantiating might somehow be the issue here.

1st time into the handler: UserAgent = "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.1.2) Gecko/20090729 Firefox/3.5.2 (.NET CLR 3.5.30729)" UrlReferrer = {localhost/testpage. Aspx} AbsoluteUri = "localhost/testpage. Aspx"; The 2nd time through is the same.It looks good to me, it is just behaving as if it hit a refresh as soon as it rendered the player.

– Keith Barrows Aug 13 '09 at 19:39 Found the problem and yes - it was in the flash app. If the browser type was FF there was an auto refresh happening (that was supposed to only fire once based on params being loaded in the flash vars). With the new services we are writing, this became an endless loop condition.

– Keith Barrows Aug 20 '09 at 16:43.

Could be you're recursively linking your pages forever :(.

My web. Config has this: On the test page there is a request to a . RIV file type which invokes the handler.

The handler returns some HTML. No other pages are involved. Maybe I am not understanding your question.

– Keith Barrows Aug 13 '09 at 17:34.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.