That was the reason in the msg I pointed to - charset on the
application/x-www-form-urlencoded. Could you try the form version
s-update-form.
I didn't think this area had changed but may a bug has been fixed since
0.2.0.
Andy
On 18/05/11 12:29, Michael Brunnbauer wrote:
re
On Wed, May 18, 2011 at 12:01:14PM +0100, Andy Seaborne wrote:
http://mail-archives.apache.org/mod_mbox/incubator-jena-users/201105.mbox/%[email protected]%3E
which is fixed in SVN (caveat the wrong SVN - see email about code move)
As to why your ruby setup is setting charset and mine does not, I don't
know.
Are you talking about the charset in the HTTP request ? There is none.
This was sniffed from the lo network interface:
POST /testupdate HTTP/1.1
User-Agent: SOH/Fuseki 0.0.0
Content-Type: application/sparql-update
Host: localhost:2021
Content-Length: 133
That isn't a application/x-www-form-urlencoded
load<http://blogspace.com/swhack/chatlogs/rdflogs/2002-06-24.rdf>
into<http://blogspace.com/swhack/chatlogs/rdflogs/2002-06-24.rdf>
There is a charset in the HTTP response:
HTTP/1.1 415 Must be application/x-www-form-urlencoded
Content-Type: text/html; charset=iso-8859-1
Cache-Control: must-revalidate,no-cache,no-store
Content-Length: 1439
Server: Jetty(6.1.25)
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1"/>
<title>Error 415 Must be application/x-www-form-urlencoded</title>
</head>
<body><h2>HTTP ERROR 415</h2>
<p>Problem accessing /testupdate. Reason:
<pre> Must be application/x-www-form-urlencoded</pre></p><hr /><i><small>Powered by
Jetty://</small></i><br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
<br/>
</body>
</html>
I have:
LANG=C
GDM_LANG=en_GB.utf8
I do not set any variables on this system which should be equivalent to LANG=C
cu,
brunni
