Why would enabling trace.axd change the way an app works?

Hi Guys,

We have a page with a flash control on, on this page the flash control allows the user to upload a file and gives a progress report. When done the tool calls another page called SaveUpload.aspx which saves the file. The tool was not able to call this page for some reason and as soon as I turned on tracing it allowed the page to be called.

Anyone seen behaviour like this before?



Make sure your trace  output is not written to page. If your Flash expects XML-based communication with server then trace may ruin it if you let ASP.NET  to write it to response stream./