I know that WebResource.axd is returning a completely empty page for a special web application request ( IIS logs showing that requests of WebResource.axd are successful (HTTP status code 200)
Copying and pasting the link in a completly blank response document in a new browser window results) > This application is complex and therefore it seems that it is an application which is doing what it is creating, Alanki I do not know.
How can I do additional debugging steps for working, why these requests are failing, and where should I look for places where application-specific behavior can affect WebResource.axd in this way ?
I have tried so far:
- Creating a new virtual directory pointing to the same directory in IIS gives the same result (empty WebResource.axd document )
- Creating an entirely new indepdent blank page and keeping it in this directory gives the same result.
- If I'm making a new virtual directory in IIS pointing to a different folder then the blank page works as expected.
- Web. Swapping of config files between work / broken directories has no effect.
It is on a Windows XP machine running IIS 5.1
It is revealed that the problem was an HTTPRPS filter filter that I was applying in the Application_PreRequestHandlerExecute method in Global.asax I was applying filters to all requests normally - even if the filter has WebResouce. If you have left the unchanged material for the axd, it still produces problems.
The following link described me in more detail and described this:
The solution is to WebResouce.axd Had to drop the filter applied.
Comments
Post a Comment