[
https://issues.apache.org/jira/browse/TIKA-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14089024#comment-14089024
]
Hudson commented on TIKA-1371:
------------------------------
SUCCESS: Integrated in tika-trunk-jdk1.6 #128 (See
[https://builds.apache.org/job/tika-trunk-jdk1.6/128/])
[TIKA-1371] Minor update to TikaLoggingFilter (sergeyb:
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1616121)
*
/tika/trunk/tika-server/src/main/java/org/apache/tika/server/TikaLoggingFilter.java
[TIKA-1371] Optional registration of new TikaLoggingFilter (sergeyb:
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1616118)
*
/tika/trunk/tika-server/src/main/java/org/apache/tika/server/TikaLoggingFilter.java
*
/tika/trunk/tika-server/src/main/java/org/apache/tika/server/TikaServerCli.java
> passing parameters via URL no longer works (regression)
> -------------------------------------------------------
>
> Key: TIKA-1371
> URL: https://issues.apache.org/jira/browse/TIKA-1371
> Project: Tika
> Issue Type: Bug
> Components: server
> Affects Versions: 1.5
> Reporter: Rob Tulloh
>
> In Tika 1.1 and 1.2, it was possible to add some values to the URL that get
> logged like this:
> http://localhost:9998/tika/GUID/FILENAME
> This was very useful for correlating between client and server in a
> distributed compute environment. In 1.5 and in the nighty builds (for 1.6),
> this feature no longer works. Not having this makes it very difficult to
> troubleshoot problems with document processing in a distributed environment.
> Please add back this feature so that operations and development teams can
> more easily figure out which tika instance is processing which document and
> what the result of the processing resulted in.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
