Because it's curl, it is sending the length.
Content-Length is necessary for keeping connections open (even if, here,
curl isn't doing that).
Sending data without Content-Length is a one-time us of connection,
which can be dropped.
If you are using curl as shown, there are no problems - the connection
is dropped on exit anyway
Could you please raise a JIRA ticket?
This isn't a point fix (though the fix looks straight forward) - there
needs to be checking in the client libraries as well.
Send my thanks to your technical support people.
Andy
On 04/03/2020 15:23, Mikael Pesonen wrote:
The error is
[2020-03-04 16:51:56] Fuseki INFO [553] POST
http://insight-dev.lingsoft.fi/ds?graph=https://resource.lingsoft.fi/graph/lsauth-demo
[2020-03-04 16:51:56] Fuseki ERROR [line: 1, col: 34] Undefined
prefix: ebucore
[2020-03-04 16:51:56] Fuseki INFO [553] 400 Parse error: [line: 1,
col: 34] Undefined prefix: ebucore (4 ms)
So it wouldn't seem odd to me if Fuseki returned the error as soon as it
sees it, since rest of the 40k of data won't affect the error.
On 04/03/2020 16.43, Andy Seaborne wrote:
What makes your tech support think that?
What operation is being called?
Andy
On 04/03/2020 13:36, Mikael Pesonen wrote:
Hi,
We have reverse proxy on Fuseki.
I'm getting this error occasionally when posting data to fuseki
dataset endpoint and data is containing some error. Instead of Fuseki
response 400 client gets 502. Our technical support thinks this might
be because Fuseki sends respond before receiving the entire data and
reverse proxy doesn't know how to handle that.
Any ideas how to handle this? Is there a setting that makes Fuseki
wait for entore input before response?
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html><head>
<title>502 Bad Gateway</title>
</head><body>
<h1>Bad Gateway</h1>
<p>The proxy server received an invalid
response from an upstream server.<br />
</p>
<hr>
<address>Apache/2.4.18 (Ubuntu) Server at xxx.fi Port
443</address>
</body></html>
Thanks!
