locked
WebResource.axd reported Error 404, images - 403.1 - Forbidden RRS feed

  • Question

  • User1759600568 posted

    Hi guys!

    We decided to run broken link checker on huge ASP.NET site on staging server (Win 2003 & IIS6). This could also act as a small load test.

    so far so good but I've noticed two main reports:

    • WebResource.axd with one specific parameter reported Error 404.0 - file not found
    • some requests to images (.gif) reported Error 403.1 - Forbidden

    These errors are logged on IIS log. 

    This is quite strange because when I try to run them in the browser manually everything is fine. The hardware seems not very loaded

    Any thoughts and inputs are highly appreciated.

    P.S. this is crossposted to ASP.NET Forums too as I didn't know which is appropriate one....

    Thanks in advance,
    Galin Iliev
    www.galcho.com

    Wednesday, January 16, 2008 11:01 AM

Answers

  • User-823196590 posted

    Strange yes.  403.1 specifically mean execute access forbidden.
    http://support.microsoft.com/kb/318380

    It seems as if your link checker is trying to submit request that execute the gifs.

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Wednesday, January 16, 2008 12:58 PM
  • User1759600568 posted

    yep, at least this is a clue....

    actually from log I see that link checker uses HEAD request and it seems this one fails...

    Is it possible HEAD request to image cause execute action on the server?

     

    Thanks for your assistance

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Wednesday, January 16, 2008 2:38 PM

All replies

  • User-823196590 posted

    Strange yes.  403.1 specifically mean execute access forbidden.
    http://support.microsoft.com/kb/318380

    It seems as if your link checker is trying to submit request that execute the gifs.

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Wednesday, January 16, 2008 12:58 PM
  • User1759600568 posted

    yep, at least this is a clue....

    actually from log I see that link checker uses HEAD request and it seems this one fails...

    Is it possible HEAD request to image cause execute action on the server?

     

    Thanks for your assistance

    • Marked as answer by Anonymous Tuesday, September 28, 2021 12:00 AM
    Wednesday, January 16, 2008 2:38 PM
  • User1759600568 posted

    Finally I was able to resolve the issue...

    Anyone interested can read about the solution on my blog.

    Thanks for helping me

    Wednesday, February 6, 2008 4:16 AM