[jira] [Commented] (TIKA-4216) Avoid checking for ImageMagick if image processing is disabled in TesseractOCRParser

[ https://issues.apache.org/jira/browse/TIKA-4216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17829593#comment-17829593 ] Josh Burchard commented on TIKA-4216: - Will this automatically backport to 2.9.2?  If

[jira] [Commented] (TIKA-4050) Forked child logs are overwritten upon restart

[ https://issues.apache.org/jira/browse/TIKA-4050?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17743175#comment-17743175 ] Josh Burchard commented on TIKA-4050: - Hey Tim. Thanks for the response. I poked aroun

[jira] [Created] (TIKA-4050) Forked child logs are overwritten upon restart

Josh Burchard created TIKA-4050: --- Summary: Forked child logs are overwritten upon restart Key: TIKA-4050 URL: https://issues.apache.org/jira/browse/TIKA-4050 Project: Tika Issue Type: Bug

[jira] [Updated] (TIKA-3963) HTML author isn't mapped to its dc:creator counterpart

[ https://issues.apache.org/jira/browse/TIKA-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Burchard updated TIKA-3963: Description: The 2.x migration doc ([here|https://cwiki.apache.org/confluence/display/TIKA/Migratin

[jira] [Updated] (TIKA-3963) HTML author isn't mapped to its dc:creator counterpart

[ https://issues.apache.org/jira/browse/TIKA-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Burchard updated TIKA-3963: Summary: HTML author isn't mapped to its dc:creator counterpart (was: HTML author and title aren't

[jira] [Created] (TIKA-3964) Please create a metadata flag to indicate an exception occurred

Josh Burchard created TIKA-3964: --- Summary: Please create a metadata flag to indicate an exception occurred Key: TIKA-3964 URL: https://issues.apache.org/jira/browse/TIKA-3964 Project: Tika Iss

[jira] [Created] (TIKA-3963) HTML author and title aren't mapped to their dc:x counterparts

Josh Burchard created TIKA-3963: --- Summary: HTML author and title aren't mapped to their dc:x counterparts Key: TIKA-3963 URL: https://issues.apache.org/jira/browse/TIKA-3963 Project: Tika Issu

[jira] [Closed] (TIKA-3961) When a parser exception happens, the "resourceName" key becomes "esourceName"

[ https://issues.apache.org/jira/browse/TIKA-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Burchard closed TIKA-3961. --- Resolution: Cannot Reproduce Reproduction was consistent at the time I wrote this bug, but now it's no

[jira] [Commented] (TIKA-3961) When a parser exception happens, the "resourceName" key becomes "esourceName"

[ https://issues.apache.org/jira/browse/TIKA-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682198#comment-17682198 ] Josh Burchard commented on TIKA-3961: - I'm going to close this for now.  I'm getting i

[jira] [Commented] (TIKA-3961) When a parser exception happens, the "resourceName" key becomes "esourceName"

[ https://issues.apache.org/jira/browse/TIKA-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17682185#comment-17682185 ] Josh Burchard commented on TIKA-3961: - I attached the particular file that I reproduce

[jira] [Updated] (TIKA-3961) When a parser exception happens, the "resourceName" key becomes "esourceName"

[ https://issues.apache.org/jira/browse/TIKA-3961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Burchard updated TIKA-3961: Attachment: encrypted.docx > When a parser exception happens, the "resourceName" key becomes "esourc

[jira] [Created] (TIKA-3961) When a parser exception happens, the "resourceName" key becomes "esourceName"

Josh Burchard created TIKA-3961: --- Summary: When a parser exception happens, the "resourceName" key becomes "esourceName" Key: TIKA-3961 URL: https://issues.apache.org/jira/browse/TIKA-3961 Project: Tika

[jira] [Commented] (TIKA-3293) Move most commandline options for tika-server into a config file in 2.0.0

[ https://issues.apache.org/jira/browse/TIKA-3293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17562894#comment-17562894 ] Josh Burchard commented on TIKA-3293: - [~tilman] I'm guessing this was possibly fixed

[jira] [Commented] (TIKA-3715) Pass forking env variables into forked process in tika-server

[ https://issues.apache.org/jira/browse/TIKA-3715?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17530858#comment-17530858 ] Josh Burchard commented on TIKA-3715: - Thanks for this fix, Tim! > Pass forking env v

[jira] [Commented] (TIKA-3669) CVE-2021-44832: Apache Log4j2 vulnerable to RCE via JDBC Appender when attacker controls configuration.

[ https://issues.apache.org/jira/browse/TIKA-3669?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17486550#comment-17486550 ] Josh Burchard commented on TIKA-3669: - Very nice.  Thanks Tim! > CVE-2021-44832: Apac

[jira] [Created] (TIKA-3669) CVE-2021-44832: Apache Log4j2 vulnerable to RCE via JDBC Appender when attacker controls configuration.

Josh Burchard created TIKA-3669: --- Summary: CVE-2021-44832: Apache Log4j2 vulnerable to RCE via JDBC Appender when attacker controls configuration. Key: TIKA-3669 URL: https://issues.apache.org/jira/browse/TIKA-3669

[jira] [Updated] (TIKA-3643) writeLimit for bytes in addition to characters

[ https://issues.apache.org/jira/browse/TIKA-3643?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Burchard updated TIKA-3643: Description: [~jmssiera] wrote up the enhancement request TIKA-3325 where he originally requested t

[jira] [Created] (TIKA-3643) writeLimit for bytes in addition to characters

Josh Burchard created TIKA-3643: --- Summary: writeLimit for bytes in addition to characters Key: TIKA-3643 URL: https://issues.apache.org/jira/browse/TIKA-3643 Project: Tika Issue Type: Improveme

[jira] [Commented] (TIKA-3632) Log4j appears to be running in a Servlet environment, but there's no log4j-web module available

[ https://issues.apache.org/jira/browse/TIKA-3632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17463974#comment-17463974 ] Josh Burchard commented on TIKA-3632: - Thanks for the responses [~grossws] and [~talli

[jira] [Created] (TIKA-3632) Log4j appears to be running in a Servlet environment, but there's no log4j-web module available

Josh Burchard created TIKA-3632: --- Summary: Log4j appears to be running in a Servlet environment, but there's no log4j-web module available Key: TIKA-3632 URL: https://issues.apache.org/jira/browse/TIKA-3632

[jira] [Commented] (TIKA-3560) Tika 2.0 (and 2.1) parses doc with less fidelity than using 1.24.1

[ https://issues.apache.org/jira/browse/TIKA-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17425171#comment-17425171 ] Josh Burchard commented on TIKA-3560: - Thank you Tim. The wiki looks good so far and I

[jira] [Commented] (TIKA-3560) Tika 2.0 (and 2.1) parses doc with less fidelity than using 1.24.1

[ https://issues.apache.org/jira/browse/TIKA-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419473#comment-17419473 ] Josh Burchard commented on TIKA-3560: - Thank you for all the comments, Tim.   Author i

[jira] [Commented] (TIKA-3560) Tika 2.0 (and 2.1) parses doc with less fidelity than using 1.24.1

[ https://issues.apache.org/jira/browse/TIKA-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419297#comment-17419297 ] Josh Burchard commented on TIKA-3560: - It looks like it contains some confidential inf

[jira] [Commented] (TIKA-3560) Tika 2.0 (and 2.1) parses doc with less fidelity than using 1.24.1

[ https://issues.apache.org/jira/browse/TIKA-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17419290#comment-17419290 ] Josh Burchard commented on TIKA-3560: - It's a pretty old file that's used in a test su

[jira] [Updated] (TIKA-3560) Tika 2.0 (and 2.1) parses doc with less fidelity than using 1.24.1

[ https://issues.apache.org/jira/browse/TIKA-3560?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Burchard updated TIKA-3560: Attachment: Capture.jpg > Tika 2.0 (and 2.1) parses doc with less fidelity than using 1.24.1 > -

[jira] [Created] (TIKA-3560) Tika 2.0 (and 2.1) parses doc with less fidelity than using 1.24.1

Josh Burchard created TIKA-3560: --- Summary: Tika 2.0 (and 2.1) parses doc with less fidelity than using 1.24.1 Key: TIKA-3560 URL: https://issues.apache.org/jira/browse/TIKA-3560 Project: Tika

[jira] [Created] (TIKA-3422) Excluding both WMFParser and EMFParser causes wmf instances NOT to appear at all

Josh Burchard created TIKA-3422: --- Summary: Excluding both WMFParser and EMFParser causes wmf instances NOT to appear at all Key: TIKA-3422 URL: https://issues.apache.org/jira/browse/TIKA-3422 Project: T

[jira] [Closed] (TIKA-3261) Text file is parsed by "EmptyParser" but the file does contain what looks like valid text

[ https://issues.apache.org/jira/browse/TIKA-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Burchard closed TIKA-3261. --- Resolution: Not A Bug > Text file is parsed by "EmptyParser" but the file does contain what looks > l

[jira] [Commented] (TIKA-3261) Text file is parsed by "EmptyParser" but the file does contain what looks like valid text

[ https://issues.apache.org/jira/browse/TIKA-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17258985#comment-17258985 ] Josh Burchard commented on TIKA-3261: - [~tallison] - I appreciate the reply and the ex

[jira] [Updated] (TIKA-3261) Text file is parsed by "EmptyParser" but the file does contain what looks like valid text

[ https://issues.apache.org/jira/browse/TIKA-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Burchard updated TIKA-3261: Description: I've tried to parse the attached file (please first extract choke.txt from  [^choke.zip

[jira] [Updated] (TIKA-3261) Text file is parsed by "EmptyParser" but the file does contain what looks like valid text

[ https://issues.apache.org/jira/browse/TIKA-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Burchard updated TIKA-3261: Description: I've tried to parse the attached file ([^choke.zip] ) using both 1.20 and 1.24.1.  The

[jira] [Updated] (TIKA-3261) Text file is parsed by "EmptyParser" but the file does contain what looks like valid text

[ https://issues.apache.org/jira/browse/TIKA-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Burchard updated TIKA-3261: Description: I've tried to parse a file using both 1.20 and 1.24.1.  The file appears valid when I

[jira] [Updated] (TIKA-3261) Text file is parsed by "EmptyParser" but the file does contain what looks like valid text

[ https://issues.apache.org/jira/browse/TIKA-3261?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Burchard updated TIKA-3261: Attachment: choke.zip > Text file is parsed by "EmptyParser" but the file does contain what looks >

[jira] [Created] (TIKA-3261) Text file is parsed by "EmptyParser" but the file does contain what looks like valid text

Josh Burchard created TIKA-3261: --- Summary: Text file is parsed by "EmptyParser" but the file does contain what looks like valid text Key: TIKA-3261 URL: https://issues.apache.org/jira/browse/TIKA-3261 P

[jira] [Updated] (TIKA-3141) LINUX - Tika shouldn't throw an exception for an empty TIKA_CONFIG environment variable value

[ https://issues.apache.org/jira/browse/TIKA-3141?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Josh Burchard updated TIKA-3141: Description: On my Linux box I configure Tika using the TIKA_CONFIG environment variable to point t

[jira] [Created] (TIKA-3141) LINUX - Tika shouldn't throw an exception for an empty TIKA_CONFIG environment variable value

Josh Burchard created TIKA-3141: --- Summary: LINUX - Tika shouldn't throw an exception for an empty TIKA_CONFIG environment variable value Key: TIKA-3141 URL: https://issues.apache.org/jira/browse/TIKA-3141

[jira] [Created] (TIKA-3066) notice of custom config file use only appears when using the command-line option

Josh Burchard created TIKA-3066: --- Summary: notice of custom config file use only appears when using the command-line option Key: TIKA-3066 URL: https://issues.apache.org/jira/browse/TIKA-3066 Project: T