Thanks Timothy,
I was calling tika-server through an ajax call using formdata, so I
couldn't specify the content type (as I know of), but at last I found what
caused it as when I processed RFTs in a command line, they worked fine.
FYI, this is how I call the server as follows:
$.ajax({
url: http://localhost:9998/tika/form,
type: 'POST',
data: formData,
dataType: 'json',
processData: false,
contentType: false,
})
Cheers,
Allison
On Mon, Nov 28, 2016 at 11:01 PM, Allison, Timothy B. <[email protected]>
wrote:
> This is helpful. IHow are you calling tika-server? Are you specifying a
> content-type?
>
>
>
> If I specify type=”application/rtf” or if I don’t specify a type, all is
> good. However, I get the same stacktrace that you shared if I incorrectly
> specify “application/msword”.
>
>
>
> *From:* Allison A. [mailto:[email protected]]
> *Sent:* Thursday, November 24, 2016 10:39 PM
> *To:* [email protected]
> *Subject:* Re: Tika server RTF processing
>
>
>
> Oops, I am re-posting and attaching them. It seems Ajax calls are not
> passed properly.
>
>
>
> On Thu, Nov 24, 2016 at 7:06 AM, Allison, Timothy B. <[email protected]>
> wrote:
>
> There was a bug in some RTF files in 1.13, but that was fixed in 1.14
> (TIKA-1845). We now have one rtf in our test suite for tika-server.
>
>
>
> If you turn logging on, can you share a stacktrace, or can you share the
> offending file?
>
>
>
> *From:* Allison A. [mailto:[email protected]]
> *Sent:* Tuesday, November 22, 2016 10:00 PM
> *To:* [email protected]
> *Subject:* Tika server RTF processing
>
>
>
> I am wondering if the RTF parser is working in Tika server 1.13 or 1.14
> via an Ajax call.
>
>
>
> I have tried both versions, but it seems I was not able to pass an Ajax
> call to Tika server, getting the 422 error,unprocessable entity. It worked
> fine with other MS office documents, Word, Excel, etc except RTF.
>
>
>
> Thanks in advance.
>
>
>
> Allison
>
>
>
