For Programmers: Free Programming Magazines  


Home > Archive > ASP .NET > February 2007 > .Net 2.0: urgent bug on a production server with WebResource.axd handler









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author .Net 2.0: urgent bug on a production server with WebResource.axd handler
Steve B.

2007-02-28, 7:09 pm

Hi,

We have on a production server a very strange bug.

After several hours of correct working (from 2hours to 5 hours, randomly),
the page output an error :

The WebResource.axd handler must be registered in the configuration to
process this request.

------------------------------------------------------------
<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<httpHandlers>
<add path="WebResource.axd" verb="GET"
type="System.Web.Handlers.AssemblyResourceLoader" validate="True" />
</httpHandlers>
</system.web>
</configuration>
------------------------------------------------------------


However, the web.config file actually defines this line (and this works a
long time before the error appears) :
------------------------------------------------------------
<httpHandlers>
<add path="WebResource.axd" verb="GET"
type="System.Web.Handlers.AssemblyResourceLoader" validate="True" />
<add verb="GET,HEAD,POST" path="*" type="OurAssembly.OurFactory,
OurAssembly, Version=1.0.0.0, Culture=neutral, PublicKeyToken=xxxxxxx"/>
</httpHandlers>
------------------------------------------------------------

I finally discover that the targeted resource is the standards Validators
javascript file... none of our class use this functionnality.

The added handler is a factory that capture all request to create custom
handlers (it is a cms application, so all urls does not actually exists on
the disk).

The error is quite difficult to reproduce, but we have the same error on a
developpment server, so I don't think this is an install problem.

Since this behaviour appears on a public web site, I need a solution or a
workaround quickly.. I hope there's some magician here :)

Thanks in advance,
Steve


Sponsored Links







Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive

Copyright 2010 codecomments.com