[GH-ISSUE #4] documents not processed, not supported mime type #4

Closed
opened 2026-02-25 22:30:14 +03:00 by kerem · 1 comment
Owner

Originally created by @ulrichhamann on GitHub (Feb 19, 2018).
Original GitHub issue: https://github.com/dveselov/docsbox/issues/4

I have found that tool, the api looks very simple , which I like.
Considering my current requirements it could be a good solution.

I cloned and installed from scratch and have run into known issue with rq.
After solving that by modifying the requirements.txt:
#git+https://github.com/nvie/rq.git#egg=rq
#rq
rq-scheduler==0.7.0

All services are up and running.
But unfortunately no document is successfully processed. Neither my own nor the sample inside that project:
Request:
curl -i -F "file=@docsbox/docs/tests/samples/sample.docx" http://localhost/api/v1/
Response:
HTTP/1.1 100 Continue

HTTP/1.1 400 BAD REQUEST
Server: nginx/1.4.6 (Ubuntu)
Date: Mon, 19 Feb 2018 16:06:21 GMT
Content-Type: application/json
Content-Length: 55
Connection: keep-alive

{"message": "Not supported mimetype: 'inode/x-empty'"}

Looking into container filesystem I use that files seem to be uploaded, but not transformed, and there is no id returned, what I expect.

Is it a known issue, do I something wrong?
Thanks and Kind Regards,
Uli

Originally created by @ulrichhamann on GitHub (Feb 19, 2018). Original GitHub issue: https://github.com/dveselov/docsbox/issues/4 I have found that tool, the api looks very simple , which I like. Considering my current requirements it could be a good solution. I cloned and installed from scratch and have run into known issue with rq. After solving that by modifying the requirements.txt: #git+https://github.com/nvie/rq.git#egg=rq #rq rq-scheduler==0.7.0 All services are up and running. But unfortunately no document is successfully processed. Neither my own nor the sample inside that project: Request: curl -i -F "file=@docsbox/docs/tests/samples/sample.docx" http://localhost/api/v1/ Response: HTTP/1.1 100 Continue HTTP/1.1 400 BAD REQUEST Server: nginx/1.4.6 (Ubuntu) Date: Mon, 19 Feb 2018 16:06:21 GMT Content-Type: application/json Content-Length: 55 Connection: keep-alive {"message": "Not supported mimetype: 'inode/x-empty'"} Looking into container filesystem I use that files seem to be uploaded, but not transformed, and there is no id returned, what I expect. Is it a known issue, do I something wrong? Thanks and Kind Regards, Uli
kerem closed this issue 2026-02-25 22:30:14 +03:00
Author
Owner

@dveselov commented on GitHub (Feb 21, 2018):

Closed via #5

<!-- gh-comment-id:367291686 --> @dveselov commented on GitHub (Feb 21, 2018): Closed via #5
Sign in to join this conversation.
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/docsbox#4
No description provided.