[
https://issues.apache.org/jira/browse/JENA-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13566661#comment-13566661
]
Hudson commented on JENA-387:
-----------------------------
Integrated in Jena__Development_Test #451 (See
[https://builds.apache.org/job/Jena__Development_Test/451/])
Note change for JENA-387 in release notes (Revision 1440504)
Add a Fuseki-Request-ID header to the HTTP response (JENA-387) (Revision
1440499)
Result = SUCCESS
rvesse :
Files :
* /jena/trunk/jena-fuseki/ReleaseNotes.txt
rvesse :
Files :
*
/jena/trunk/jena-fuseki/src/main/java/org/apache/jena/fuseki/mgt/ActionBackup.java
*
/jena/trunk/jena-fuseki/src/main/java/org/apache/jena/fuseki/servlets/SPARQL_ServletBase.java
*
/jena/trunk/jena-fuseki/src/main/java/org/apache/jena/fuseki/servlets/ServletBase.java
* /jena/trunk/jena-fuseki/src/test/java/org/apache/jena/fuseki/TestQuery.java
> 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
