You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jena.apache.org by "Rob Vesse (JIRA)" <ji...@apache.org> on 2013/06/27 18:23:20 UTC
[jira] [Closed] (JENA-475) HTTP Authentication for SPARQL Updates
does not actually apply authentication
[ https://issues.apache.org/jira/browse/JENA-475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rob Vesse closed JENA-475.
--------------------------
> HTTP Authentication for SPARQL Updates does not actually apply authentication
> -----------------------------------------------------------------------------
>
> Key: JENA-475
> URL: https://issues.apache.org/jira/browse/JENA-475
> Project: Apache Jena
> Issue Type: Bug
> Components: ARQ
> Affects Versions: Jena 2.10.1
> Reporter: Rob Vesse
> Assignee: Rob Vesse
> Fix For: Jena 2.10.2
>
>
> A user spotted an error in the logic for applying authentication credentials to SPARQL Updates. It turns out while we create a CredentialsProvider we fail to associate that with the HTTP Client and so fail to actually peform authentication
--
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
Re: [jira] [Closed] (JENA-475) HTTP Authentication for SPARQL
Updates does not actually apply authentication
Posted by Rob Vesse <rv...@yarcdata.com>.
No problem, unintended side effect of JENA-480 no doubt
I will add a note to the log4j properties that it may be useful to up the
level to INFO/DEBUG to aid in debugging any HTTP communication issues.
Rob
On 6/28/13 4:03 AM, "Andy Seaborne" <an...@apache.org> wrote:
>Rob - I was getting log output from
>org.apache.http.impl.SystemDefaultHttpClient
>at level INFO when running the ARQ test suite.
>
>I've changed the log4j properties to include
>
># Apache Commons HTTP
>log4j.logger.org.apache.http=WARN
>
>
> Andy
Re: [jira] [Closed] (JENA-475) HTTP Authentication for SPARQL Updates
does not actually apply authentication
Posted by Andy Seaborne <an...@apache.org>.
Rob - I was getting log output from
org.apache.http.impl.SystemDefaultHttpClient
at level INFO when running the ARQ test suite.
I've changed the log4j properties to include
# Apache Commons HTTP
log4j.logger.org.apache.http=WARN
Andy