[
https://issues.apache.org/jira/browse/JENA-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13508767#comment-13508767
]
Hudson commented on JENA-358:
-----------------------------
Integrated in Jena__Development_Test #310 (See
[https://builds.apache.org/job/Jena__Development_Test/310/])
JENA-358
Upgrade hhtpclient/httpcore
Use SystemDefaultHttpClient, which respects system settings. (Revision 1416542)
Result = SUCCESS
andy :
Files :
* /jena/trunk/jena-arq/pom.xml
* /jena/trunk/jena-arq/src/main/java/org/apache/jena/riot/HttpOp2.java
* /jena/trunk/jena-arq/src/main/java/org/openjena/riot/web/HttpOp.java
* /jena/trunk/jena-fuseki/pom.xml
> 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
> Fix For: Jena 2.10.0
>
> Attachments: vcs-diff2729498539859018600.patch
>
>
> 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
