-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't set the headers #1
Comments
Thank you very much for the reply. |
After adding the --cors whateverClient line to the entrypoint
But I couldn't manage to put or post any image or pdf yet. |
Hey there,
Thank you for this image. It works great on desktop.
I am trying to use it on Google Cloud Run.
I deployed it after changing some of the environment variables and it was perfect.
It works perfectly on desktop. A screenshot from a Georgian language news channel OCR'ed perfectly. But there is an issue with the cloud version
I can't set the headers on the build that's uploaded to the cloud
For example I can't set the X-Tika-OCRLanguage header via postman. I can send the png file via binary (and not multiform) and it renders OCR on default languages which are eng+rus+ara. Please note that I have apt-get tesseract-oct-all on the dockerfile.
I only get this WARN in the logs section:
WARN Both org.apache.tika.server.resource.TikaResource#getHTML and org.apache.tika.server.resource.TikaResource#getText are equal candidates for handling the current request which can lead to unpredictable results
Do I need an extra Header to send to the Tika?
What do you think about this? This is a common problem in all the images I have came across in the wild.
Is this a CORS issue? Do you know a way to fix this? Maybe it requires a new config on the tika-config.template.xml?
Best,
The text was updated successfully, but these errors were encountered: