UpdateProcessRemote and UTF-8

[Phil Coates <ph...@sparqlr.com>]

Hello,

I think I've found a bug with UpdateProcessRemote that seems to affect at
least 3.0.1 and 3.1.0.

As far as I can tell, UTF-8 characters are fine up to the point where
they're passed off, but the UpdateProcessRemote object loses any charset
information when it submits the query:

HttpOp.execHttpPost(endpoint, WebContent.contentTypeSPARQLUpdate, reqStr,
null, getHttpContext(), getAuthenticator()) ;

At this point, WebContent.contentTypeSPARQLUpdate is
"application/sparql-update", rather than "application/sparql-update;
charset=utf-8", etc.

Have I missed something?

Many thanks,

Phil Coates.

*Philip Coates*

philip.coates@sparqlr.com
skype:philip.coates.76
Tel: +44 (0)7711 818384

*SemanticIntegration* <http://www.semanticintegration.co.uk/>

Re: UpdateProcessRemote and UTF-8

[Andy Seaborne <an...@apache.org>]

On 08/08/16 17:24, Phil Coates wrote:
> Hello,
>
> I think I've found a bug with UpdateProcessRemote that seems to affect at
> least 3.0.1 and 3.1.0.
>
> As far as I can tell, UTF-8 characters are fine up to the point where
> they're passed off, but the UpdateProcessRemote object loses any charset
> information when it submits the query:
>
> HttpOp.execHttpPost(endpoint, WebContent.contentTypeSPARQLUpdate, reqStr,
> null, getHttpContext(), getAuthenticator()) ;
>
> At this point, WebContent.contentTypeSPARQLUpdate is
> "application/sparql-update", rather than "application/sparql-update;
> charset=utf-8", etc.
>
> Have I missed something?
>
> Many thanks,
>
> Phil Coates.
>
> *Philip Coates*
>
> philip.coates@sparqlr.com
> skype:philip.coates.76
> Tel: +44 (0)7711 818384
>
> *SemanticIntegration* <http://www.semanticintegration.co.uk/>
>

application/sparql-update has a default charset of utf-8.

https://www.w3.org/TR/sparql11-update/#mediaType

In fact, it is only defined for utf-8.

Are you seeing actual errors? If so, where?

	Andy