awarnier wrote:
>
> Glynbach2 wrote:
>> The answer came from the IIS forums. In IIS 6 I also needed to add a Web
>> Service Extension for the redirect dll and set it to be 'Allowed'.
>> Haven't
>> had to do that in previous versions of IIS
Thanks for your help. There is a new IIS permissionings section for filters,
I had to add a new web extension there and all was good.
--
View this message in context:
http://old.nabble.com/IIS-redirect-stops-at--xxx--is-a-servlet-url---should-redirect-to-ajp13-tp26495411p26499936.html
Sent from
The answer came from the IIS forums. In IIS 6 I also needed to add a Web
Service Extension for the redirect dll and set it to be 'Allowed'. Haven't
had to do that in previous versions of IIS and afaik it's not in the how to
either.
--
View this message in context:
http://old.nabble.com/IIS-redi
awarnier wrote:
>
> Just to try to eliminate the obvious :
> - is Tomcat really listening on port 8009 ?
> "netstat -an" will tell you.
> - is port 8009 not being blocked by the Windows firewall or such ?
> you can slso try "telnet localhost 8009" (if it works, Tomcat will
> accept and then
Hi, I am having problems with IIS redirect using IIS6, Tomcat 6 and JRE6. The
servlet can be accessed on :8080 but gives a 404 error on :80.
I've done redirect on older machines with no problems in the past, but I
can't find the problem here, I also am stuck as to what my next debugging
step shou