[
https://issues.apache.org/jira/browse/TIKA-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14019202#comment-14019202
]
Sergey Beryozkin commented on TIKA-1323:
----------------------------------------
Hi Tim, sure, I was only commenting because in a pure web service server world
it is kind of a good practice to limit the exposure of the exception
information to the client for the security reasons. But in this case it is not
a 'pure' server fault which can expose some sensitive info, it is more about
presenting the 'fault' info about given file Tika can not process to the
client, this is how I see it a least :-). So yes, if A works for you then it is
+1...
Cheers, Sergey
> Improve exception reporting in JAX-RS server
> --------------------------------------------
>
> Key: TIKA-1323
> URL: https://issues.apache.org/jira/browse/TIKA-1323
> Project: Tika
> Issue Type: Improvement
> Reporter: Tim Allison
> Priority: Minor
>
> I'd like to use tika-server for TIKA-1302. As part of that, I'd like to
> record exception stacktraces per document. I see two options: transmit the
> info back to the client (assuming a doc didn't bring the server down :) )
> along with the current error code or log the document id and stacktrace via
> the server. Given my current design thoughts, I'd prefer the first option.
> Any objections or recommendations?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
