Webresource.axd HttpHandler (Compression, Caching, Debug issues)

In ASP.NET 2.0 all client-side validations/postback functionality is done via Webresource.axd HttpHandler unlike ASP.NET 1.X (when all javascript functions were placed inside aspnet_client folder locally). This can cause some issues for example with compression, caching and debug.

See for example - Webresource.axd compression workaround issue. Also looks like that it never get cached in debug mode.

I wondered whether these issues might be solved directly. And it turns out that Webresource.axd could be easily found in Temporary Internet Files, since it returns pure javascript and it is possible to copy it and/or open it with notepad. I wonder if it is possible to manage the functionality provided by Webresource.axd without the use of HttpHandler but from the physical location (aka ASP.NET 1.X way) when you copy the file. Interesting whether it is possible to do it in elegant way to solve different kinds of compression/caching problems.

The original idea by Arno Janse van Rensburg.

Related Posts:

• ASP.NET 2.0: How do I Video Series is Available
• Bug in ASP.NET rendering hyperlink
• This site is running on ASP.NET 2.0 (2)
• ASP.NET 2.0: Http Compression and WebResource.axd
• New in .NET 2.0: ConfigurationManager.AppSettings Property
• Asp.Net: Hierarchical Repeater Control
• Asp.Net 2.0: Provider Model
• Jeff Prosise talks about Asynchronous Pages in ASP.NET 2.0
• Asp.Net Atlas: ProgressBar and Binding sample code
• Asp.Net Atlas: master-detail page sample code

<Previous comment didn't come through... trying again>

Anatoly, did you get an answer for this question eventually?

My Facebook app doesn't work because of this Webresource.axd, because Facebook server can't fetch the file.