Details
-
Bug
-
Status: Closed
-
Minor
-
Resolution: Fixed
-
ARQ 2.9.4
-
None
Description
As i found, the remote SPARQL Update execution uses Apache HttpClient 4.1 which do not honor JVM proxy settings while the SPARQL Query execution does not rely on the HttpClient and the JVM proxy settings can be applied.
Maybe the HttpOp class could use SystemDefaultHttpClient from HttpClient v4.2 instead of DefaultHttpClient.