[
https://issues.apache.org/jira/browse/TIKA-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071631#comment-14071631
]
Rob Tulloh commented on TIKA-1371:
----------------------------------
Also, I was trying out the detect/stream URL that is documented on the Tika wiki
http://wiki.apache.org/tika/TikaJAXRS
and that doesn't seem to work either. I tried both tika/detect/stream and
detect/stream
2014-07-23_11:32:59.68485 WARNING: No operation matching request path
"/tika/detect/stream" is found, Relative Path: /detect/stream, HTTP Method:
PUT, ContentType: */*, Accept: */*,. Please enable FINE/TRACE log level for
more details.
2014-07-23_11:33:21.14176 WARNING: No operation matching request path
"/detect/stream" is found, Relative Path: /detect/stream, HTTP Method: PUT,
ContentType: */*, Accept: */*,. Please enable FINE/TRACE log level for more
details.
> 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)
