Published on: Friday, March 16th 2012

Debugging a bad WebResource.axd request

Authors

Name
Steve McNiven
Twitter
@stevemcniven

Telerik has a great blog post on how to figure out where a bad WebResource.axd request is coming from.

When you use firebug you just see a string of seemingly garbage appended to WebResource.axd. The post by Hristo gives you an aspx page you can drop into your site which will accept that WebResource URL and decrypt if for you!

decrypting_the_url_and_getting_the_resource_name

Boost your online presence.

Let us create the perfect digital experience for your company.