On 1/7/06, Bill Barker <[EMAIL PROTECTED]> wrote:
> DefaultServlet inherits doOptions from HttpServlet. This works correctly
> (and, has back at least to the Sevlet-2.2 days), and is why Servlets rarely
> have to implement it. If you had index.html instead of index.jsp, you would
> see exactly w
"Costin Manolache" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
On 1/7/06, Bill Barker <[EMAIL PROTECTED]> wrote:
>
> Which is exactly what the JSP spec says it should do, and why Remy was
> absolutely correct to consider that this is a users@ question. It's up to
> the page autho
On 1/7/06, Bill Barker <[EMAIL PROTECTED]> wrote:
>
> Which is exactly what the JSP spec says it should do, and why Remy was
> absolutely correct to consider that this is a users@ question. It's up to
> the page author to decide how to deal with the request method.
The page author is us, index.js
"Mark Thomas" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Mark Thomas wrote:
>> Mauro Bertapelle wrote:
>>>this has nothing to do with
>>>webdav and the naive
>>>way in which ie implements it, but probably Tomcat should handle
>>>"options" better when
>>>it's acting as a static
DefaultServlet doesn't implement OPTIONS either, and I don't remember
ever implementing or seeing an implementation of the method in
anything except webdav servlet.
Since it is part of the standard - and it seems it is even used - we
should support it, but this has been broken forever. I'm curious
Mark Thomas wrote:
> Mauro Bertapelle wrote:
>>this has nothing to do with
>>webdav and the naive
>>way in which ie implements it, but probably Tomcat should handle
>>"options" better when
>>it's acting as a static web server.
>>
>>Mauro
>
> I have confirmed this behaviour with the latest source f
Mauro Bertapelle wrote:
> Costin,
>
> you've got the point I was trying to make, this has nothing to do with
> webdav and the naive
> way in which ie implements it, but probably Tomcat should handle
> "options" better when
> it's acting as a static web server.
>
> Mauro
I have confirmed this beh
William A. Rowe, Jr. wrote:
> Costin Manolache wrote:
>
>> I'm curious - why would you need the options method ?
>>
>> Obviously, as you found, tomcat does not support it ( and many other
>> servers ), and I never heard of any use of it, even if it is in the
>> spec.
>>
>> Well, in theory servlets
Costin Manolache wrote:
I'm curious - why would you need the options method ?
Obviously, as you found, tomcat does not support it ( and many other
servers ), and I never heard of any use of it, even if it is in the
spec.
Well, in theory servlets could respond to 'options' method if they
choose
Costin,
you've got the point I was trying to make, this has nothing to do with
webdav and the naive
way in which ie implements it, but probably Tomcat should handle
"options" better when
it's acting as a static web server.
Mauro
--
Costin Manolache wrote:
I guess the problem was that the d
I guess the problem was that the default servlet ( part of tomcat )
doesn't handle options for static files like "/", instead returns the
page as if it would be a GET. I tried on www.apache.org - and apache
seems to return the right thing ( no body, etc ).
Costin
On 1/6/06, Keith Wannamaker <[EM
Tomcat "handles" it just fine -- if you implement it in your servlet :-)
Options conveys not only whether a resource is dav-enabled and the
class of dav support, but it has a well-defined xml response body for a
number of ACL and DeltaV properties, all of which needs to be handled by
the appli
Interesting.
Well, Remy is the expert in webdav, but I guess you'll need to talk
with him on the users list :-)
I suppose the default servlet could handle 'options', since it's part
of the standard, but for regular servlets there is nothing to be done,
it's up to them to implement whatever method
Costin,
I'm tweaking with internet explorer and his web folder feature (access to
webdav resource).
When accessing a webdav resource, ie fire a lot of "OPTIONS" requests,
not only to the specified url but as you see from my example even to the
"/" uri
which is obviously catched by the default s
I'm curious - why would you need the options method ?
Obviously, as you found, tomcat does not support it ( and many other
servers ), and I never heard of any use of it, even if it is in the
spec.
Well, in theory servlets could respond to 'options' method if they
choose to - and so could the defa
Mauro Bertapelle wrote:
oops, sorry I wasn't sure where to post it
Ok. If you have questions about usage of Tomcat, you should post on
[EMAIL PROTECTED]
Rémy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional comman
oops, sorry I wasn't sure where to post it
mauro
--
Remy Maucherat ha scritto:
Mauro Bertapelle wrote:
Is it correct that coyote reply with the home page contents on an HTTP
OPTIONS method request ?
If you post another message on this list that belongs to the user
list, I'll ban you.
Mauro Bertapelle wrote:
Is it correct that coyote reply with the home page contents on an HTTP
OPTIONS method request ?
If you post another message on this list that belongs to the user list,
I'll ban you.
Rémy
-
To unsubsc
Is it correct that coyote reply with the home page contents on an HTTP
OPTIONS method request ?
Client request:
OPTIONS / HTTP/1.1\r\n
Request Method: OPTIONS
Request URI: /
Request Version: HTTP/1.1
Translate: f\r\n
User-Agent: Microsoft Data Access Internet Publishing Provide
Is it correct that coyote reply with the home page contents on an HTTP
OPTIONS method request ?
Client request:
OPTIONS / HTTP/1.1\r\n
Request Method: OPTIONS
Request URI: /
Request Version: HTTP/1.1
Translate: f\r\n
User-Agent: Microsoft Data Access Internet Publish
20 matches
Mail list logo
