Bad Request (400) from Jetty when accessing URL with no '/' at end

[stigkj]

Cannot connect to an URL without a '/' at the end, for example:

• http://google.com -- Bad Request (400)
• http://google.com/ -- OK

Debugged just a little bit, and I can see that the betamax Jetty handler is not called for the first case. Not sure why, though.

Have you seen this before?

I tried both using Jersey and curl from the command line and got the same problem on both.

[robfletcher]

This is caused by JETTY-1553. It looks like there was a fix committed to a later version of Jetty.

Betamax has avoided upgrading Jetty since later versions introduced compatibility problems (particularly with Grails projects) caused by a breaking API change in SLF4J. I'll see if I can figure out what specific version fixed this issue & whether I can upgrade to it without breaking anything.

[robfletcher]

Well, it's not fixed in _ 7.6.5.v20120716_ which is the latest version of the Jetty 7 branch. Upgrading to Jetty 8 may be more problematic.

[robfletcher]

Oh boy. Jetty 8 means upgrading to Servlet 3.0 API (and I'm still not sure it will fix the problem)

[robfletcher]

Still not fixed in Jetty 8

[robfletcher]

This is fixed by moving from Jetty to Netty – #66