[
https://issues.apache.org/jira/browse/JENA-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13558678#comment-13558678
]
Rob Vesse commented on JENA-348:
--------------------------------
I was unable to apply your patch file from Jan 16th successfully and the older
Nov 17th patch appears to be superceded by that patch.
Can you please update your working copy to the latest revision and regenerate
the patch file again?
NB - Atlassian tools automatically version attachments so uploading with the
same file name as a previous attachment will supercede the previous patch file
but still preserve the old version for future reference.
> Support HTTP auth for SPARQL Update requests
> --------------------------------------------
>
> Key: JENA-348
> URL: https://issues.apache.org/jira/browse/JENA-348
> Project: Apache Jena
> Issue Type: Improvement
> Components: ARQ
> Affects Versions: ARQ 2.9.4
> Reporter: Sören Brunk
> Priority: Minor
> Attachments: jena-348-1.patch, jena-348.patch, UpdateAuthExample.java
>
>
> ARQ supports HTTP Basic Authentication for read queries
> (setBasicAuthentication() in QueryEngineHTTP).
> I can't find authentication support for SPARQL Update though. The responsible
> class UpdateProcessRemote uses HttpOp as an abstraction, and HttpOp in turn
> encapsulates HttpClient from Apache HTTP Components.
> So I guess a way to go would be to extend HttpOp to support auth or to expose
> the HttpClient object in order to set auth options as described in [1].
> I'm happy to help if I can get some hints about the preferred way to include
> auth support.
> [1]
> http://hc.apache.org/httpcomponents-client-ga/tutorial/html/authentication.html
--
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
