Encoded slashes in the uid part of the path cause a 400

[GoogleCodeExporter]

This is a problem when trying to support openID uids which will often
contain slashes.

To reproduce this:
1. Create an account in the spring config with a slash in the username
2. Use curl to try to POST to it. E.g.:

curl -u mike/jones:potato -i -X POST
http://localhost:8080/Caboto-Web/annotation/person/mike%2Fjones/public/ -d
'title=A%20Title&description=A%20description&type=SimpleComment&annotates=http%3
A%2F%2Fexample.org%2Fthing'

3. This gives a 400. I don't think it touches the caboto code - perhaps it
is being bounced at the jersey level?

Original issue reported on code.google.com by Jasper.T...@gmail.com on 21 Nov 2008 at 10:39

[GoogleCodeExporter]

I think this was a tomcat issue. See org.apache.catalina.connector. 
CoyoteAdapter.ALLOW_BACKSLASH on 
http://tomcat.apache.org/tomcat-5.5-doc/config/systemprops.html

I tested with jetty and it worked ok. Then I ran tomcat with the switch above 
set to true. It worked too.

Original comment by Jasper.T...@gmail.com on 19 Aug 2010 at 1:28

• Changed state: Done