Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Feb 27, 2013 10:56 PM by NickLocke
Feb 27, 2013 10:56 PM|LINK
I have a series of ASPX pages which are returning handcrafted JSON using response.write (long story, but that's where we are). There is some third party software which calls the ASPX pages and then processes the JSON that is returned. That third party
software can be told of a problem by being given a 500 HTTP Status. When given that, it displays a nice error.
If I run the app locally, and cause it to throw an appropriate exception, the exception is caught by the app, the app returns a 500 and some text and all is well.
Exactly the same app deployed to Azure, and cause it to throw the same exception, the app does not return the 500 and my text. Instead, it returns a full-blown HTML error 500 page.
I'm struggling to work out why the app behaves differently in this way when running in Azure.
Any thoughts? Thanks,