tomcat-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Robert Priest <>
Subject RE: ISAPI Filter and OPTIONS Dav Method.
Date Wed, 01 May 2002 16:53:45 GMT
Thanks. I will give those debugging items a try and get back to you.

>Dies? you are saying that it hangs in any way? or the filter continues
>behaving after that OPTIONS request ?

Perhaps "dies" is the wrong word to use. What I mean to describe is that
after HttpFilterProc() finishes processing(and it does seem to
finish),somewhere in the process between IIS and the call to
HttpExtensionProc, I get the "500 Internal Server Error" sent back down to
the client. 

No, IIS does not hang. I will try to be more exact in the future.


-----Original Message-----
From: Ignacio J. Ortega []
Sent: Wednesday, May 01, 2002 12:26 PM
To: 'Tomcat Users List'
Subject: RE: ISAPI Filter and OPTIONS Dav Method.

> De: Robert Priest []
> Enviado el: miƩrcoles 1 de mayo de 2002 16:03

BTW: this is starting to be an excellent bug report !! so please post it
to bugzilla ( if it's no there already ) so we can follow it better ..
> Using: 
> Tomcat 4.0.3.
> Slide 1.0.16.
> ISAPI Filter from J-T-C
> WebDrive 5.1 (Client)
> IIS 5.0

Excelent, thanks..

> I have been having an issue where the ISAPI Filter dies 
> whenever receiving
> an OPTIONS request.

Dies? you are saying that it hangs in any way? or the filter continues
behaving after that OPTIONS request ?

> It looks like HttpFilterProc gets called and does it work, 
> but somewhere
> between IIS doing something and the
> call to HttpExtensionProc, the server sends back a "500 
> Internal Server
> Error"

One way to be completely sure of who is generating that error 500 is to
try to add a debug="9999" attribute to the ajp13 connector in
server.xml, in tomcat 3.3 we got a nice logs about whats sending and
receiving tomcat from IIS..

One way to debug the connection between IIS and tc, is to use a external
iis server ( or external tomcat ) and reconfigure the configs to use
that host for ajp13 instead of localhost, this way you will be able to
see commns in port 8009 over the wire, and you could see if the options
request is saw by tc in any way..

> Does anyone have any idea what may be going on.

No, but with your work and some more time, we will catch it.. sure :),
btw.. excellent work in this message..

> Just to test what would happen, I hacked the HttpFilterProc 
> method to to
> catch when an OPTIONS request is received and return 
> a OPTIONS response.  I made the HttpFilterProc method, at 
> that point, return
> with a "SF_STATUS_REQ_FINISHED". With that, I can connect to 
> the server and
> get a list of folders and files through the client. I can 
> even copy out from
> the client to my desktop. However, I do encounter another 
> "500 Internal
> Server Error" when I attempt a "PUT" (to add a file). 

> I say that to say this: there is obviously a problem in the 
> filter with it
> not passing headers (the method in particular) back to IIS or 
> from IIS to
> the
> HttpExtensionProc method. As I am not that proficient is IIS 
> dev soI have
> not  a clue what is happening. Is an IIS  header missing or something?

> Is this the correct "chain"  for the request:
> IIS -> filter ->IIS -> extension -> AJP13 Connector -> Tomcat -> Web
> Application (in this case: slide 1.0.16)

Yes it is, my guess now is that your having problems in the extension
part, i gues that because the Filter processing is very thin, a matter
of getting the correct worker and forward the entire thing to the
correct extension, some heraders adde and cganged otheres.. that's all,
i doubt the problems lies in the filter, you could try to move your fake
response code to the extension instead the filter, this way we can
surpass the filter as the your problems source..

Saludos ,
Ignacio J. Ortega

To unsubscribe:   <>
For additional commands: <>
Troubles with the list: <>

To unsubscribe:   <>
For additional commands: <>
Troubles with the list: <>

View raw message