I have been able to track down the problem, but I don't know whether it's been solved yet in the JK 1.x code.
The problem has to do with the way the ISAPI filter registers itself with IIS. An ISAPI filter can specify the events within IIS that it responds to. The Tomcat filter specifes that it responds to the SF_NOTIFY_AUTH_COMPLETE event on IIS 5. The problem is that OPTIONS requests are not authenticated by IIS, and therefore never trigger an SF_NOTIFY_AUTH_COMPLETE event. I believe that in JK2, the filter can be configured to respond to the SF_NOTIFY_PREPROC_HEADERS event instead. Also, the ISAPI filter that came with Tomcat 3.3 responds to the SF_NOTIFY_PREPROC_HEADERS event rather than SF_NOTIFY_AUTH_COMPLETE. I haven't tried to get JK2 working yet--I just downgraded to the Tomcat 3.3 ISAPI filter. That version, however, has another problem, related to the proprietary Microsoft "Translate" header used by IIS and Web Folders. We resolved that with a custom filter that removes the Translate header from the request. I can provide more details about this problem off-list if you like. Also see http://msdn.microsoft.com/library/default.asp?url=/library/en-us/iisref/html/psdk/asp/isgu744y.asp (or http://makeashorterlink.com/?K1E726FA2) for more information about IIS events. -- Tim Moore / Blackboard Inc. / Software Engineer 1899 L Street, NW / 5th Floor / Washington, DC 20036 Phone 202-463-4860 ext. 258 / Fax 202-463-4863 > -----Original Message----- > From: Joakim Str�m [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, December 04, 2002 11:01 AM > To: Tomcat Users list > Subject: Problem with http OPTIONS using mod_jk for IIS > > > > Hello, > > I have tried to use JK2 with IIS but ran into a problem with > corrupted files (posted earlier on this list). I'm not sure > about the status of JK2 (is it still in beta?) > > So now I am trying with the older mod_jk 1.2.1. But in this > case, all HTTP OPTIONS requests are turned down with status > 500 internal server error code. The options requests never > enter my servlet code. > > I found a similar question which has been posted earlier to Bugzilla: > http://nagoya.apache.org/bugzilla/show_bug.cgi?id=8709 The problem description seems identical to what I am experiencing. Does anybody recall whether that case was settled, and what caused this behavior? Or have any ideas about the problem? Thanks in advance, Joakim Strom System Architect, Excosoft -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]> -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
