geronimo-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "D. Strauss" <geron...@ds-2.de>
Subject Jetty vs. encoded URLs
Date Thu, 13 Jul 2006 17:37:56 GMT
Hello, Jetty users

a new problem has occured:

[ResourceCache] Alias request of
'file:/opt/geronimo-1.1/repository/Testapp/Ear1/1.0/Ear1-1.0.ear/w2.war/register.jspx;jsessionid=5d54fc882vp54'
for
'file:/opt/geronimo-1.1/repository/Testapp/Ear1/1.0/Ear1-1.0.ear/w2.war/register.jspx;jsessionid=5d54fc882vp54

This and a friendly 404 by Jetty

HTTP ERROR: 404

/register.jspx;jsessionid=5d54fc882vp54

RequestURI=/raid/register.jspx;jsessionid=5d54fc882vp54

Powered by Jetty://



is the only answer that I get when I access the register.jspx with my
webbrowser. Basically, the problem is that Jetty tries to find a file
named "register.jspx;jsessionid=...". That fails, of course ;) Seems
that Jetty doesn't know that this request contains a JSESSIONID. What do
I have to do to get Jetty recognize this encoded url? Is there a special
setting for this?

Best regards

Dirk

Mime
View raw message