[jira] [Commented] (JENA-572) ARQ should provide a convenient way to set the User-Agent for HTTP requests

["Rob Vesse (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JENA-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13805430#comment-13805430 ] 

Rob Vesse commented on JENA-572:
--------------------------------

I will commit a fix shortly, it adds a setUserAgent() method to HttpOp for configuring the desired User-Agent string.

It applies the configured User-Agent header to all requests, by default if not otherwise configured the value "Apache-Jena-ARQ/VERSION" where VERSION is read from ARQ.VERSION will be used.

Users can choose to disable sending a User-Agent header by calling HttpOp.setUserAgent(null);

> ARQ should provide a convenient way to set the User-Agent for HTTP requests
> ---------------------------------------------------------------------------
>
>                 Key: JENA-572
>                 URL: https://issues.apache.org/jira/browse/JENA-572
>             Project: Apache Jena
>          Issue Type: Improvement
>          Components: ARQ
>    Affects Versions: Jena 2.11.0
>            Reporter: Rob Vesse
>            Assignee: Rob Vesse
>             Fix For: Jena 2.11.1
>
>
> As discussed over at https://github.com/pyvandenbussche/sparqles/issues/9 as of 2.11.0 ARQ provides centralised HTTP operations which allows for setting global HTTP configuration.
> One thing that it would be particularly useful to set is the User-Agent header so that people using ARQ to write RDF/SPARQL robots can assign an appropriate User-Agent to their requests.
> Currently we do not change the header at all so sites will see the generic Apache HttpClient User-Agent header.



--
This message was sent by Atlassian JIRA
(v6.1#6144)