From dev-return-27883-apmail-jena-dev-archive=jena.apache.org@jena.apache.org Fri Sep 14 17:43:09 2018 Return-Path: X-Original-To: apmail-jena-dev-archive@www.apache.org Delivered-To: apmail-jena-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id EA7B1216A1 for ; Fri, 14 Sep 2018 17:43:08 +0000 (UTC) Received: (qmail 16228 invoked by uid 500); 14 Sep 2018 17:43:03 -0000 Delivered-To: apmail-jena-dev-archive@jena.apache.org Received: (qmail 16184 invoked by uid 500); 14 Sep 2018 17:43:02 -0000 Mailing-List: contact dev-help@jena.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@jena.apache.org Delivered-To: mailing list dev@jena.apache.org Received: (qmail 16102 invoked by uid 99); 14 Sep 2018 17:43:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 14 Sep 2018 17:43:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 7338CC0331 for ; Fri, 14 Sep 2018 17:43:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -110.301 X-Spam-Level: X-Spam-Status: No, score=-110.301 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id yYNcLbSp8I26 for ; Fri, 14 Sep 2018 17:43:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id 29A515F4A9 for ; Fri, 14 Sep 2018 17:43:01 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 68AD0E1013 for ; Fri, 14 Sep 2018 17:43:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 1F29623F9E for ; Fri, 14 Sep 2018 17:43:00 +0000 (UTC) Date: Fri, 14 Sep 2018 17:43:00 +0000 (UTC) From: "Niraj Patel (JIRA)" To: dev@jena.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Created] (JENA-1604) Add request hook for HTTP query execution MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 Niraj Patel created JENA-1604: --------------------------------- Summary: 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 I am using Jena's QueryEngineHTTP for queries and RemoteUpdateRequest for u= pdates. I would like to send a custom header that will differ on each reque= st. Our database, Allegrograph, allows us to pass down custom headers while= querying or updating in order to store that information in access logs. Fo= r each SPARQL request we want to send down unique request markers and usern= ames in order to be able to trace from a UI click to backend calls to queri= es 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 Ht= tp Client wouldn't work in this case.=C2=A0The suggestion [~andy.seaborne]= =C2=A0made was to create a request hook in=C2=A0HttpOp where we could add a= dditional headers as necessary.=C2=A0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)