[
https://issues.apache.org/jira/browse/JENA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566650#comment-13566650
]
Andy Seaborne commented on JENA-387:
------------------------------------
Tested. Works for all SPARQL protocol types and all requests (error or
successful) that reach the Fuseki server. 404's due to no matching dispatch
handled by Jetty alone and don't show up, which is fine, and inevitable if
hosted in a larger environment.
Minor: I renamed the getRequestId as allocRequestId because it has a side
effect of inc the counter so it's not a simple getter to me.
> Include Fuseki request count in header
> --------------------------------------
>
> Key: JENA-387
> URL: https://issues.apache.org/jira/browse/JENA-387
> Project: Apache Jena
> Issue Type: Improvement
> Components: Fuseki
> Affects Versions: Fuseki 0.2.5
> Reporter: Leigh Dodds
> Assignee: Rob Vesse
> Priority: Minor
> Fix For: Fuseki 0.2.6
>
>
> When Fuseki is logging requests it uses a unique number for each query. It
> would be useful if this number was included in the headers for the query
> response. This would make it slightly easier to trace back errors to the
> Fuseki logs
--
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
