|
If you were logged in you would be able to see more operations.
|
|
The RESTful HTTP protocol for Sesame 2 should support multibyte characters properly. Encoding such characters in URLs or URL-parameters for GET-requests has proven to be very problematic. The %xx escape sequences can only encode characters in the range of 0 - 255. Character encodings specified in headers only apply to request bodies. How encoded characters in the URL are handled is platform dependent; some apply the specified encoding, some apply the system's default encoding and some allow you to configure a specific encoding.
To be on the safe side, the HTTP protocol should allow clients to encode multibyte characters to some ASCII-string before URL-encoding these values. This specifically applies to the 'context' and 'baseURI' parameter in the current protocol, as these are used in non-POST requests. A suitable option is to use N-Triples/Turtle syntax for encoding URIs, blank nodes and literals.
Note: parameters in POST requests are safe wrt character encoding as these are send to the server in the body of the request.
|
|
The server and HttpSail have been updated to encode GET parameters that can contain multi-byte characters using NTriples encoding. I still need to create a test-case for this in the TCK, but I'm marking this issue as resolved.
|
|
Improvement
Resolved
Minor
Support multibyte characters in HTTP protocol