It's weird that a javascript throwing a server side error and it seems like this happens only when the client browser is Firefox.
The page loads without any issues, but a 500 log is reported in iis log.
Any help would be deeply appreciated.
From http://www.developmentnow.com/g/59_0_0_0_0_0/inetserver-iis.htm
Posted via DevelopmentNow.com Groups
http://www.developmentnow.com/g/
Not sure why IIS would think that, but does that provide any clues?
Cheers
Ken
--
--
Microsoft MVP - Windows Server (IIS)
MCITP (x2), MCTS (x8), MCSE+Security, MCDBA
M.BT (UNSW)
http://www.adOpenStatic.com/blog
"mukmac" <nos...@developmentnow.com> wrote in message
news:cbd794fc-0a87-4e10...@developmentnow.com...
It looks like you have configured IIS to process *.gif with a custom
ISAPI Extension. Please identify the ISAPI Extension and determine
what is causing it to fail with 500.
There is no javascript throwing server-side error. If it can reliably
happen to Firefox, then you can use it to debug what is causing the
failure.
The page did not load without issue. The page APPEARED to load BECAUSE
the browser client has already cached /images/tip.gif sometime ago. If
the browser client flushed its cache of tip.gif, this 500 error will
show up.
At this point, this does not look like an ASP.Net nor IIS issue. The
problem is with what you have configured to process *.gif on IIS.
Track that down.
For example, you may have configured aspnet_isapi.dll as wildcard
application mapping so that ASP.Net modules/handlers are active on
*.gif requests, and one of those modules/handlers decided to balk for
some reason. You will have to chase through your server and software
configuration to figure this out since you are causing the issue for
yourself...
//David
http://w3-4u.blogspot.com
http://blogs.msdn.com/David.Wang
//