[
https://issues.apache.org/jira/browse/TIKA-1621?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14525116#comment-14525116
]
Hudson commented on TIKA-1621:
------------------------------
SUCCESS: Integrated in tika-trunk-jdk1.7 #660 (See
[https://builds.apache.org/job/tika-trunk-jdk1.7/660/])
Update CHANGES entry for TIKA-1621. (mattmann:
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1677280)
* /tika/trunk/CHANGES.txt
- fix for TIKA-1621: TikaResource should log errors determining
ContentDisposition (mattmann:
http://svn.apache.org/viewvc/tika/trunk/?view=rev&rev=1677279)
*
/tika/trunk/tika-server/src/main/java/org/apache/tika/server/resource/TikaResource.java
> TikaResource should log errors determining ContentDisposition
> -------------------------------------------------------------
>
> Key: TIKA-1621
> URL: https://issues.apache.org/jira/browse/TIKA-1621
> Project: Tika
> Issue Type: Bug
> Components: server
> Affects Versions: 1.8
> Reporter: Chris A. Mattmann
> Assignee: Chris A. Mattmann
> Fix For: 1.9
>
>
> I ran into a problem in tika-python that took me a while to track down - I
> was passing a full file path as Content-Disposition instead of just the file
> name. The reason it was so hard to track down was that we swallow the error
> in TikaResource if there is an issue determining the attachment and
> disposition, etc. I'd like to simply print the exception and stack trace.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
