On Wed, Jul 20, 2011 at 22:06, Michael Hunger <michael.hun...@neotechnology.com> wrote: > what is the concrete error that happens if you send over that space + slash > encoded property?
Returned by HTTP console on Neo4j server (but the behaviour is the same in my Python client): - Regular property key: http> PUT http://localhost:7373/db/sylva/node/3537/properties/pröp€rtŷ "un\u00ed\u00a9od e/v\u00e4l\u00fa\u00ea" ==> 204 No Content - Property key with spaces invalidate the URL: http> PUT http://localhost:7373/db/sylva/node/3537/properties/pr öp€rtŷ "un\u00ed\u00a9od e/v\u00e4l\u00fa\u00ea" ==> Invalid JSON data. I can fix this URL encoding the key and decoding in the client. - Property key with slahs crash the URL: http> PUT http://localhost:7373/db/sylva/node/3537/properties/pr/öp€rtŷ "un\u00ed\u00a9od e/v\u00e4l\u00fa\u00ea" ==> 404 Not Found I can fix this with safe URL encoding. - Propery key with slash and spaces: http> PUT http://localhost:7373/db/sylva/node/3537/properties/pr ö/p€rtŷ "un\u00ed\u00a9od e/v\u00e4l\u00fa\u00ea" ==> Invalid JSON data. I'm not able to fix this becaus If a use safe URL encoding, the spaces are converted into "+" characters in the server, and that's not the key i want to store. Sorry for the difficulty to reproduce the bug. Regards. -- Javier de la Rosa http://versae.es _______________________________________________ Neo4j mailing list User@lists.neo4j.org https://lists.neo4j.org/mailman/listinfo/user
