Hi All,

 I have an issue with IIS 6.0, multiple websites, and an HttpModule.

I have two distinct websites, let's call them WebA and WebB, running on IIS 6.0, not virtual directories but websites. They each have their own application pool. They each have their own physical directories. Their physical directories are not sub-directories of the other's physical directory, they are distinct. They each have their own Web.Config.

WebA has the HttpModule registered in its Web.Config. WebB does not have the HttpModule registered in its Web.Config. But requests that are made to WebB are being processed through the HttpModule registered for WebA.

Can anyone explain why this is happening, and if possible, how to fix it?

                     Thanks in Advance,
                                 SBSSrDev

Maybe try adding to the web.config a <clear/> tag

Hi,

 I can try that, but I'm looking for a more elegant solution because we're running several web sites on this web server. Also, I'd like to understand why this is happening as from all the documentation I've read, my understanding is that it shouldn't be happening. Can anyone help out?

                Thanks,
                     SBSSrDev

Make sure that you have not added the custom HttpModule declaration in the
machine.config.

Otherwise, When you say that you have two different sites, Are they running
on different ports ?

--
Madhur

"SBSSrDev" wrote in message news:2319992@forums.asp.net...
> Hi,
>
> I can try that, but I'm looking for a more elegant solution because we're
> running several web sites on this web server. Also, I'd like to understand
> why this is happening as from all the documentation I've read, my
> understanding is that it shouldn't be happening. Can anyone help out?
>
> Thanks,
> SBSSrDev
>

Hi,

 Thanks again for the input. The matter was actually put to rest. Turns out the production support folks were reporting this as an issue but upon investigation in to the matter it turned out that this issue did not exist and was being confused with another matter. Just to address outstanding questions:

1. No, the module was not added to Machine.Config. If it had been, it would be expected that all sites on that framework pass requests through that module.

2. Yes, these sites were operating on different Host Headers and different ports. Further, we now have 2 sites on the same web server on the same ports, just with different Host Headers and this is still not issue.

Thanks for all the help all, sorry it was as easy as a false alarm.

                      - SBSSrDev