SamuelBoerlin commented on issue #3345: URL: https://github.com/apache/jena/issues/3345#issuecomment-3149423271
> The curl example suggests the problem is server side or networking - until now we haven't had evidence whether it is server-side, environment or or the Jena client side code sending the request. But the "exit 0" from curl is strange although these large fetches are done "streaming" style - the HTTP response does not include the HTTP response size because it is not known when the response starts. I tried reproducing this behaviour with a simple chunk-encoded Python HTTP server. As you say, since the HTTP response does include the response size header, the client cannot know whether a response was actually complete or not. Though if the HTTP server (or network connection I expect) is killed outright during the transfer, then `curl` fails as expected because the connection is not closed gracefully. So I think we can also rule out a network issue, because it would seem that the connection was actually closed gracefully because `curl` exited with 0. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
