[
https://issues.apache.org/jira/browse/JENA-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15375060#comment-15375060
]
ASF GitHub Bot commented on JENA-576:
-------------------------------------
Github user rvesse commented on the issue:
https://github.com/apache/jena/pull/151
My major concern with this pull request is that it replaces a nicely
encapsulated API with requiring users to directly interact with a lower level
API. It seems like there should be room for compromise i.e. Keeping
`HttpAuthenticator` but perhaps having it simply operate over a
`HttpClientBuilder` instead
I am also unclear how more complex authentication such as forms based
authentication which requires some sort of out of band login and presenting
some token with each request e.g. a cookie. Part of the reason the original API
was introduced by myself was that I needed to interact with systems that relied
upon forms based authentication. As I understand that the proposed new API I
would have to manage that login myself and pass the resulting `HttpContext`
everywhere that needs it?
> Upgrade Apache HTTP Client to 4.3
> ---------------------------------
>
> Key: JENA-576
> URL: https://issues.apache.org/jira/browse/JENA-576
> Project: Apache Jena
> Issue Type: Dependency upgrade
> Components: ARQ
> Affects Versions: Jena 2.11.0
> Reporter: Rob Vesse
> Assignee: Rob Vesse
> Priority: Minor
> Original Estimate: 72h
> Remaining Estimate: 72h
>
> As of 2.11.0 ARQ centralizes all HTTP operations through HttpOp which relies
> on Apache HTTP Client. Currently we are using 4.2.3 while the latest stable
> release is actually 4.3.1
> Therefore we should look at upgrading our code to use the latest version
> which may entail some refactoring since there appears to have been some
> breaking changes across the minor version bump which users have seen in usage
> - e.g.
> https://github.com/pyvandenbussche/sparqles/issues/9#issuecomment-27220738
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
