Version? IIRC there was a fix around here not so long ago.
On 13/09/13 12:41, Martynas Jusevičius wrote:
This is probably the correct encoded value (including slashes etc):
http%3A%2F%2Flocalhost%3A8080%2Fgraphs%2F2013%2520Danfoss%2520MPHE.xlsx
http%3A%2F%2Flocalhost%3A8080%2Fgraphs%2F2013%2520Danfoss%2520MPHE.xlsx
I agree ... and so does the code :-) because I have just C&P that string
from a debugger onto the dev codebase.
It uses the rules for URI component encoding (if I got them right).
On Fri, Sep 13, 2013 at 1:35 PM, Martynas Jusevičius
<[email protected]> wrote:
Hey,
I'm using DatasetAdapter to access a Graph Store. It seems to me
however that it is not properly escaping graph URI when building the
request URI.
What did you get?
4.2 Indirect Graph Identification
(http://www.w3.org/TR/sparql11-http-rdf-update/#indirect-graph-identification)
gives an example of "encoded graph URI". That is, graph URI
http://localhost:8080/graphs/2013%20Danfoss%20MPHE.xlsx
should appear as
.../store?graph=http://localhost:8080/graphs/2013%2520Danfoss%2520MPHE.xlsx
in the request URI. However I cannot see that DatasetAdapter is doing
such escaping
DatasetGraphAccessorHTTP.target()
(it was easier to find the code on GrepCode than on
Apache):
http://grepcode.com/file/[email protected][email protected]@org$apache$jena$fuseki$http$DatasetAdapter.java
This results in 400 Bad Request if graph URI has special characters
like in this case. Can we call this a bug?
Martynas
graphityhq.com
Andy
