Can't fully utilize TUS protocol

[yasakova-anastasia]

My actions before raising this issue

• Read/searched the docs
• Searched past issues

Expected Behaviour

Current Behaviour

TUS protocol supposes a leading HEAD request to retrieve file state on the server. Server supports this, but traefik converts these HEAD requests to GET, and then server rejects it. Thus, we cannot continue an interrupted file uploading.

Workaround: both UI and SDK always send files from scratch. It leads to:

• more user traffic
• possible filename conflicts (partially uploaded files are not autoremoved)

Possible Solution

Steps to Reproduce (for bugs)

Context

Your Environment

• Git hash commit (git log -1):
• Docker version docker version (e.g. Docker 17.0.05):
• Are you using Docker Swarm or Kubernetes?
• Operating System and version (e.g. Linux, Windows, MacOS):
• Code example or link to GitHub repo or gist to reproduce problem:
• Other diagnostic information / logs:
  Logs from `cvat` container

Issue by @zhiltsov-max

[SpecLad]

After investigation, I found out that traefik is innocent. The one converting the requests is actually mod_wsgi, as explained here. I'm currently investigating if it would be safe to turn this functionality off (I believe it should be).

[zhiltsov-max]

Great news! The checks in the function suggest to look at the configuration parameters.

[SpecLad]

@zhiltsov-max The description says that there's a workaround in the UI to always send files from scratch, but I don't see where this workaround is implemented. It seems like the UI just uses tus-js-client normally. Does this workaround actually exist?

[zhiltsov-max]

@SpecLad. Speaking about UI, I don't remember checking the library itself (maybe I did, but I just don't remember). I see there is a comment about the implementation that "we try, and if it fails, we start from scratch".