[
https://issues.apache.org/jira/browse/JENA-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507308#comment-13507308
]
Andy Seaborne commented on JENA-358:
------------------------------------
Upgrading (to a GA release) looks sensible and then the switch to
SystemDefaultHttpClient is natural.
Do you have a patch for this?
> Remote SPARQL Update requests do not honor JVM proxy settings while queries do
> ------------------------------------------------------------------------------
>
> Key: JENA-358
> URL: https://issues.apache.org/jira/browse/JENA-358
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: ARQ 2.9.4
> Reporter: Simon Gabor
> Assignee: Andy Seaborne
> Priority: Minor
>
> 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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
