You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Simon Gabor (JIRA)" <ji...@apache.org> on 2012/11/29 21:56:58 UTC
[jira] [Created] (JENA-358) Remote SPARQL Update requests do not
honor JVM proxy settings while queries do
Simon Gabor created JENA-358:
--------------------------------
Summary: 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
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
[jira] [Commented] (JENA-358) Remote SPARQL Update requests do not
honor JVM proxy settings while queries do
Posted by "Hudson (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Commented] (JENA-358) Remote SPARQL Update requests do not
honor JVM proxy settings while queries do
Posted by "Simon Gabor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507988#comment-13507988 ]
Simon Gabor commented on JENA-358:
----------------------------------
Added patch for jena-arq upgrading httpcore 4.2.3 GA and httpclient 4.2.2 GA and switching to SystemDefaultHttpClient.
I was able to use proxy with SPARQL update queryies.
> 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
> 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
[jira] [Commented] (JENA-358) Remote SPARQL Update requests do not
honor JVM proxy settings while queries do
Posted by "Andy Seaborne (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (JENA-358) Remote SPARQL Update requests do not
honor JVM proxy settings while queries do
Posted by "Simon Gabor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Simon Gabor updated JENA-358:
-----------------------------
Attachment: vcs-diff2729498539859018600.patch
> 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
> 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
[jira] [Resolved] (JENA-358) Remote SPARQL Update requests do not
honor JVM proxy settings while queries do
Posted by "Andy Seaborne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne resolved JENA-358.
--------------------------------
Resolution: Fixed
Fix Version/s: Jena 2.10.0
Patch applied and now in SVN - thanks.
> 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
[jira] [Assigned] (JENA-358) Remote SPARQL Update requests do not
honor JVM proxy settings while queries do
Posted by "Andy Seaborne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne reassigned JENA-358:
----------------------------------
Assignee: Andy Seaborne
> 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
[jira] [Commented] (JENA-358) Remote SPARQL Update requests do not
honor JVM proxy settings while queries do
Posted by "Simon Gabor (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13507986#comment-13507986 ]
Simon Gabor commented on JENA-358:
----------------------------------
Patch upgrading apache httpcomponents & use SystemDefaultHttpClient
> 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
> 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
[jira] [Closed] (JENA-358) Remote SPARQL Update requests do not
honor JVM proxy settings while queries do
Posted by "Andy Seaborne (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JENA-358?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Andy Seaborne closed JENA-358.
------------------------------
> 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