Get Help:Ask a Question in our Forums|Report a Bug|More Help Resources
Last post Jul 15, 2009 02:05 AM by ans_anish
Jan 20, 2009 02:26 PM|LINK
We have an odd error with WebResource.axd url generation. (It does not seem to be related to the fairly common "WebRsource.axd Padding is invalid and cannot be removed" issue).
In this case, we're seeing that the WebResource.axd link turns into garbage past a certain point, replaced by what looks like contents from the actual resource. Worse yet, it seems to be fairly inconsistant.
In our case, the link should (and usually does look like):
All well and good. However, we are getting errors logged from users...and the url they're trying to access looks like (in one case):
Stranger yet, we got a few of these in rapid succession from the same user, who was apparently trying to reload the page...each url slightly different.
Has anyone seen anything like this?
WebResource.axd invalid corrupted url
Jan 23, 2009 09:05 AM|LINK
(It does not seem to be related to the fairly common "WebRsource.axd Padding is invalid and cannot be removed" issue).
I think you can get some ideas from this links:
Jan 23, 2009 01:06 PM|LINK
Um...I said I don't think it's related to that issue...
We don't actually get that error, and the other symptoms aren't the same either. I just mentioned that error because it seems to be the only thing that I could find information on for WebResource.axd, and it comes up a lot in answers, but that it doesn't
seem to be what's happening here.
Apr 18, 2009 02:20 PM|LINK
something like this WebResource.axd?d=t6XQ9u7g%20%20%20%20%20%20%20%20%20%20alt='';
padded with whitespace and url encoded?!?!?!
I also gathered the browser info
IsNewSession: ''False''; SessionID: ''gkqtrb45ieip5r2gblinrs55''; Type = ''IE8'' ; Name = ''IE'' ; Version = ''8.0'' ; Major Version = ''8'' ; Minor Version = ''0'' ; Platform = ''WinXP'' ; Is Beta = ''False'' ; Is Crawler = ''False'' ; Is AOL = ''False''
I am wondering if I should scrape the output of my pages applictaiont_endrequest to see if I am handing out these bad urls?
I cannot recreate the issue....could be some crappy symantec software seeing the script url and not liking it ?!?!?!
anyone got a fix for me?!?!?!
Apr 19, 2009 04:46 PM|LINK
I´m having exactly the same problem here. Anybody solved this?
Apr 20, 2009 03:07 AM|LINK
I have seen several of these errors now
I have only seen it with IE8 so far. but that may not mean anything.....
Apr 28, 2009 09:38 PM|LINK
So I looked closer at the IIS Website and noticed that the aspnet_client folder wast still in the directory hosting my website. As I understand it this folder was necessary in asp.net 1 and 1.1 but not in 2. I removed the folder and then was able to remove
the WebResource.axd file. So the production server is now like the test server. I am hoping that this will also solve the weird WebResource.axd urls I am seing requested from clients in the error log. ..... I hope....
Apr 29, 2009 02:30 AM|LINK
didnt work. still getting the wierd urls for the webresource.axd.....
Apr 30, 2009 07:59 PM|LINK
I have come to the conclusion that this is likely not a problem with the html that is being served, but rather with the way that html is being parsed by IE, in particular IE 8. Each case we've seen has been with IE 8 or, in a few cases 7...but IE 8 will
pretend to be IE 7 if it is in compatibility mode. My suspicion is that the IE parser is getting confused, and creating these bizarre results. Has anyone else encountered these types of problems?
Apr 30, 2009 08:08 PM|LINK
I thought that too though I have seen the problem with other versions of IE 6,7 and 8. I think it might be related to the script tags and the CDATA in relation to the DOCTYPE and HTML4 strict versus transitional. but I am guessing at this point. baffeled
and confused.....this sucks. i like microsoft generally but its hard to convince people its good technology when shit like this messing things up!!!