jruby-rack-1.1.x can not handle PUT/DELETE request

[mkristian]

with jruby-rack I get
HTTP/1.1 405 HTTP method PUT is not supported by this URL
when I sent a PUT request to the server. same for DELETE. see my gist how to reproduce it

https://gist.github.com/2952760

[kares]

reminds me of #105 and that one has been fixed in 1.1.6 good you make sure you're using that version ?!

if it still does not work and since you seem to be the jetty-run owner maybe you could tell us how jruby-rack is setup (filter/servlet) so we do not have to digg down the source ...

[mkristian]

with 1.1.6 it does not work with 1.0.10 everything works. did not try any immediate versions. I added the web.xml I am using to https://gist.github.com/2952760

jetty-run just starts jetty with that webapp +web.xml inside the rails directory. POST and GET do work. if you need a context.xml for a standalone jetty, I should be able to provide it (do what the jetty-maven-plugin in does manually). jetty version is 7.6.4.v20120524 - did not try higher versions.

[mkristian]

I tried all different versions - so version 1.1.1, 1.1.4 and 1.0.10 are working. 1.1.3 does reach rails but has a stream problem. version 1.1.5 and 1.1.6 do show the reported problem.

same behaviour with jetty 8.1.4.v20120524

[kares]

I see, it's caused by a refactoring we did in how the filter handles it's up chain, previously it "swallowed" all error outcomes.
Now it checks for a specific error 404 (and due Tomcat 403 since it's the reference impl and returns it on PUT/DELETEs) otherwise assumes the request is handled by the chain and does return the response (without dispatching to Rails).

There are 2 ways you can work-around this on 1.1.6:

1. do not use the RackFilter if you do not need it's behavior - use the RackServlet instead
2. you might configure the "unhandled" responses with a filter init-paramater responseNotHandledStatuses

As a resolution of this issue I'll most likely add HTTP 405 to the default responses list as well ...

[mkristian]

thanx for adding 405 - it will keep jetty on the same level of support as tomcat :)