[
https://issues.apache.org/jira/browse/TIKA-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14072046#comment-14072046
]
Rob Tulloh commented on TIKA-1371:
----------------------------------
Perfect! Though I have to say the examples on the wiki are not exactly clear.
Just tried this and it worked as expected. Thank you.
One more thought on the URL, if Tika just logged what it received, we could
pass the extra context via parameters like this:
http://localhost:9998/tika?guid=XXX
I test this and it worked for producing the correct result.
If Tika server could just log the URL received, that would help immensely in
the distributed world where many clients interact with Tika server and
correlation is useful for diagnosing what was sent where.
> 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)
