[
https://issues.apache.org/jira/browse/TIKA-1371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14071625#comment-14071625
]
Rob Tulloh commented on TIKA-1371:
----------------------------------
In tika 1.2, we pass a URL
http://HOST:9998/tika/GUID/FN
that results in this kind of log in the tika log:
2014-07-23_06:53:16.57840 INFO: tika/10083908/n/a (text/html)
When we use the same approach in tika 1.5
curl -T http://localhost:9998/123456/x.csv
we see this in the tika log
2014-07-23_11:23:33.92903 WARNING: No operation matching request path
"/tika/123456/x.csv" is found, Relative Path: /123456/x.csv, HTTP Method: PUT,
ContentType: */*, Accept: */*,. Please enable FINE/TRACE log level for more
details.
2014-07-23_11:23:33.93747 Jul 23, 2014 6:23:33 AM
org.apache.cxf.jaxrs.impl.WebApplicationExceptionMapper toResponse
2014-07-23_11:23:33.93749 WARNING: javax.ws.rs.ClientErrorException
2014-07-23_11:23:33.93750 at
org.apache.cxf.jaxrs.utils.JAXRSUtils.findTargetMethod(JAXRSUtils.java:503)
2014-07-23_11:23:33.93753 at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.processRequest(JAXRSInInterceptor.java:218)
2014-07-23_11:23:33.93753 at
org.apache.cxf.jaxrs.interceptor.JAXRSInInterceptor.handleMessage(JAXRSInInterceptor.java:90)
2014-07-23_11:23:33.93754 at
org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:272)
2014-07-23_11:23:33.93754 at
org.apache.cxf.transport.ChainInitiationObserver.onMessage(ChainInitiationObserver.java:121)
2014-07-23_11:23:33.93755 at
org.apache.cxf.transport.http_jetty.JettyHTTPDestination.serviceRequest(JettyHTTPDestination.java:35
> 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)
