Ok, it seems that you're right about %2f and / being different.

The slash is one of a few reserved characters defined in section 2.2 of RFC2396.

Other characters can safely be unencoded in the URL. For example, 
http://test.com/%7efoo/ is 100% equivalent to http://test.com/~foo/.

Canonicalization algorithms are described in section 2.4.2. It seems that 
adherence to these rules are rare through.

For the sake of simplicity across platforms and frameworks, irrespective of how 
well they follow 2.4.2, I think a JSON payload is the safest approach.


-- Tatham


-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Tatham Oddie
Sent: Tuesday, 20 September 2011 11:04 AM
To: Neo4j user discussions
Subject: Re: [Neo4j] Forward slashes in index values

Great! :)

Re: the URLs being the same, check out http://www.google.com.au/intl/en/about/ 
vs http://www.google.com.au/intl/en%2fabout/
Both load just fine.

I'll go trudging through the URI spec to work out if this is correct behaviour 
or not later.


-- Tatham


-----Original Message-----
From: [email protected] [mailto:[email protected]] On 
Behalf Of Jim Webber
Sent: Monday, 19 September 2011 9:32 PM
To: Neo4j user discussions
Subject: Re: [Neo4j] Forward slashes in index values

Hi Tatham,

I don't necessarily agree with %2f and / being the same, but I do agree that 
POSTing everything in the URI is a bit quirky.

Peter's opened up a new issue on this: 

https://github.com/neo4j/community/issues/25

And I get to hack on it. So it looks like the REST index API will be changing 
in our 1.5 release to have a JSON payload in the entity body. That should 
prevent any URI ambiguity and be more sensible too.

Jim
_______________________________________________
Neo4j mailing list
[email protected]
https://lists.neo4j.org/mailman/listinfo/user
_______________________________________________
Neo4j mailing list
[email protected]
https://lists.neo4j.org/mailman/listinfo/user
_______________________________________________
Neo4j mailing list
[email protected]
https://lists.neo4j.org/mailman/listinfo/user

Reply via email to