[
https://issues.apache.org/jira/browse/JENA-1604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16615203#comment-16615203
]
A. Soroka commented on JENA-1604:
---------------------------------
[~nirajpatel], can you take a look at the above PR? Would that suit your use
case? You would need to define one transformer object that is used on all
requests, but it would have full access to each request and could tap into
other state or computation as needed.
> Add request hook for HTTP query execution
> -----------------------------------------
>
> Key: JENA-1604
> URL: https://issues.apache.org/jira/browse/JENA-1604
> Project: Apache Jena
> Issue Type: Task
> Components: Jena
> Reporter: Niraj Patel
> Assignee: A. Soroka
> Priority: Critical
>
> I am using Jena's QueryEngineHTTP for queries and RemoteUpdateRequest for
> updates. I would like to send a custom header that will differ on each
> request. Our database, Allegrograph, allows us to pass down custom headers
> while querying or updating in order to store that information in access logs.
> For each SPARQL request we want to send down unique request markers and
> usernames in order to be able to trace from a UI click to backend calls to
> queries that were performed in the graph. I did some digging around and it
> seems like it's not possible. Using default headers when configuring Apache's
> Http Client wouldn't work in this case. The suggestion [~andy.seaborne] made
> was to create a request hook in HttpOp where we could add additional headers
> as necessary.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
