Wanted to add that we are using Rails 2.3

A workaround is to set jetty's dirAllowed init param to false. Though I'd be curious to know what changed between 1.0.1 and 1.0.3.

I'm using embedded jetty with a default WebAppContext. I didn't see an easy way to disable dirAllowed programmaticly, so I instead copied org/eclipse/jetty/webapp/webdefault.xml from the jar to my project, updated dirAllowed, and then told jetty to use it with:
myWebAppContext.setDefaultsDescriptor(updatedCopyOfDefaultWebXml);

Karthik, what server are you using? I did try to make some changes in 3bf46978 for Jetty servers, but if it was working before in 1.0.1 I'm a bit confused, as jeffContext says.

Can you try this jar file:

http://snapshots.repository.codehaus.org/org/jruby/rack/jruby-rack/1.0.4.dev-SNAPSHOT/jruby-rack-1.0.4.dev-20101130.193134-1.jar

Whoops, you said that the current trunk fails too. Any chance you can bisect back to a known working version?

Nick, the behavior is fine with v1.0.1. Is that your question?

Karthik, just wondering if you can figure out what commit broke the behavior after the 1.0.1 release.

Also, what container and version are you using?

Think I fixed this in 1.0.6. Let's try it.