By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
426,179 Members | 2,192 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 426,179 IT Pros & Developers. It's quick & easy.

asp.net httphandler won't invoke

P: n/a
Hi,

I am using a third party win 2003 iis 6.0 to serve my website.
The web site has a httphandler which does some custom jobs.

When I try to invoke the httphandler from some url call, it won't start

and give a 404 error on the url.

I personally create a plain win 2003 iis 6.0 server locally. The
httphandler works fine.

Is there anything in asp.net prevent invoking a httphandler? And what
are the fixes?

Thanks,

qwerty

Nov 19 '05 #1
Share this Question
Share on Google+
14 Replies


P: n/a
Hi Qwerty,

What version of the .NET Framework are you using? I have had issues
with ASP.NET 2.0 and HttpHandlers. Check out the following article on
my blog for details and see if it helps:

http://tod1d.blogspot.com/2005/01/se...net-20-on.html

Did you build this HttpHandler yourself? How do you specify what
extension should use the HttpHandler? Normally you do this in either
the Machine.Config or Web.Config of the application.

Tod Birdsall, MCP
http://tod1d.blogspot.com

Nov 19 '05 #2

P: n/a
We are using win 2003, iis 6.0, web.config for declaring httphandler.

Our team build this HttpHandler. We specific the handler in web.config
as follow

<httpHandlers>
<add verb="*" path="*.yyy" type="xx.zz, xx" />

And delcare the ".yyy" mapping in iis 6.0 configuration.

It works in a plain vanilla win 2003 iis 6.0 that I build but it does
not work with a third party win 2003 iis 6.0

No idea on this mysterious behaviour. One indication is that the custom
fake URL is being serve and give a 404 error instead of grabbing the
".yyy" extension and invoking the httphandler.

Please help.

qwerty

Nov 19 '05 #3

P: n/a
could it be that the server hoster has to map request for your extension to
the asp.net dll, so your handler can actually pick up the request

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

"qwerty" <ar*****@wowgao.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...
We are using win 2003, iis 6.0, web.config for declaring httphandler.

Our team build this HttpHandler. We specific the handler in web.config
as follow

<httpHandlers>
<add verb="*" path="*.yyy" type="xx.zz, xx" />

And delcare the ".yyy" mapping in iis 6.0 configuration.

It works in a plain vanilla win 2003 iis 6.0 that I build but it does
not work with a third party win 2003 iis 6.0

No idea on this mysterious behaviour. One indication is that the custom
fake URL is being serve and give a 404 error instead of grabbing the
".yyy" extension and invoking the httphandler.

Please help.

qwerty

Nov 19 '05 #4

P: n/a
Hi Qwerty,

Something similar happened to me, but when I specified the
<httpHandlers> tag in the Web.config it worked fine. I just told IIS to
have the .NET Framework handle that particular extension. What does
your entry in IIS look like?

Tod Birdsall, MCP
http://tod1d.blogspot.com

Nov 19 '05 #5

P: n/a
Qwerty, do I know you from win32asm? This is Doc.
Nov 19 '05 #6

P: n/a
To drhowarddrfinedrhoward ,

No, sorry I don't do win32asm. It may be another qwerty.

Nov 19 '05 #7

P: n/a
This following is my entry in apps mapping

executable: ...\v1.1.4322\aspnet_isapi.dll
extension: .yyy
Verbs: All Verbs
Script engine: checked
Check that file exists: unchecked

Nov 19 '05 #8

P: n/a
Shouldn't it be ...\v1.1.4322\aspnet_isapi.dll?

qwerty

Nov 19 '05 #9

P: n/a
it should probably be if thats the version, is it mapped in IIS

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

"qwerty" <ar*****@wowgao.com> wrote in message
news:11**********************@f14g2000cwb.googlegr oups.com...
Shouldn't it be ...\v1.1.4322\aspnet_isapi.dll?

qwerty

Nov 19 '05 #10

P: n/a
Yes

Nov 19 '05 #11

P: n/a
I have talked to the third party and they even give me screen cap (a
while ago). There should be nothing wrong in the "normal" setup. The
version of .net framework should be correct. Something might be hidden.
Is there anything that will "intercept" the request "before" the
httphandler?

Nov 19 '05 #12

P: n/a
There are handlers in the isapi pipeline that may (will) have priority over
your own, but logically if its configured correctly to pass requests to your
extension through the asp.net dll and the web.config entries are correct
then it should work. The pipeline will get to your handler in due course.

I would pass your hosting company a copy of your setup on your own machine,
so they can mimic it and see if it works. If your handler does anything odd
with the pages then it may be a permissions problem.

--
Regards

John Timney
ASP.NET MVP
Microsoft Regional Director

"qwerty" <ar*****@wowgao.com> wrote in message
news:11**********************@o13g2000cwo.googlegr oups.com...
I have talked to the third party and they even give me screen cap (a
while ago). There should be nothing wrong in the "normal" setup. The
version of .net framework should be correct. Something might be hidden.
Is there anything that will "intercept" the request "before" the
httphandler?

Nov 19 '05 #13

P: n/a
I asked them to check metabase.xml as well.

However, the last time I checked with the third party, everything
starts to work. The problem solved.

Thanks everyone for the inputs.

qwerty

Nov 19 '05 #14

P: n/a
I asked them to check metabase.xml as well.

However, the last time I checked with the third party, everything
starts working. The problem solved.

Thanks everyone for the inputs.

qwerty

Nov 19 '05 #15

This discussion thread is closed

Replies have been disabled for this discussion.