[
https://issues.apache.org/jira/browse/TIKA-1779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14968302#comment-14968302
]
Tim Allison commented on TIKA-1779:
-----------------------------------
My guess: you typically only get Content-Length if the underlying stream is a
FileInputStream. When you call tika-app, that is opening a FileInputStream.
tika-server, however, tries to parse the stream as is without buffering to disk
and then opening a FileInputStream...so no Content-Length.
Are there other content differences?
> different outputs between cmd & srv version
> -------------------------------------------
>
> Key: TIKA-1779
> URL: https://issues.apache.org/jira/browse/TIKA-1779
> Project: Tika
> Issue Type: Bug
> Components: batch
> Affects Versions: 1.10
> Environment: Intel Core I5 4GB Ram, Notebook
> OS: debian8, x64, Gnome
> java version "1.8.0_60"
> Java(TM) SE Runtime Environment (build 1.8.0_60-b27)
> Java HotSpot(TM) 64-Bit Server VM (build 25.60-b23, mixed mode)
> ruby 2.2.3p173 (2015-08-18 revision 51636) [x86_64-linux]
> Reporter: tranquillo
>
> [ruby] I see strange behaviour, a difference between tika runs via console or
> as a server. The xml output called via the console contains one line more
> meta (<meta name="Content-Length" content="26845"/> ), but from the cmd-run
> the complete file is 337 lines long whereas the output from the
> server-version is 444 lines long.
> The input file is here:
> http://ratsinfo.dresden.de/getfile.php?id=12174&type=do
> console cmd line:
> $ java -server -Djava.awt.headless=true -jar 'tika-app.jar' --xml
> '~/data/0012174.pdf'
> the request against the server:
> curl -T '~/data/0012174.pdf' http://localhost:9998/tika --header "Accept:
> text/xml"
> Is here is a possibility to upload files, please give me a hint, otherwise i
> put the two files on my server for a while.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
