Clarify that POST is an optional step

[tus]

Clarify that POST is an optional step

[vayam]

I think it is a good idea to make the initial POST request optional. That makes it flexible to integrate with existing upload flows.

If we make POST optional, then I would think we should make Content-Type mandatory as part of PUT requests

PUT /files/24e533e02ec3bc40c387f1a0e460e216 HTTP/1.1
Host: tus.example.org
Content-Type: video/mp4
Content-Length: 100000
Content-Range: bytes 0-99999/200000

[felixge]

If the post is optional, how do you resume an upload that encounters an issue during the first request? I think there still needs to be some mechanism to create the resource initially, but this could be an application-specific one, instead of the proposed POST.

[vayam]

yupp, we have app specific post request that gives out video_file_id, max allowed file size based on quota, uploadserver end point to choose based on geo of client ip. Also signatures and expires param

We could internally make a POST request and map our video_file_id to upload_request_id generated by uploadserver

initial post would look like:
browser -> app server -> uploadserver
POST request would have app specific data as query params. it would be opaque. the uploadserver can interpret those app specific params.

[felixge]

I think this has been sufficiently adressed in the 0.2 release. Stuff like Content-Type etc. still needs to be defined as part of the meta data extension, but that's a separate discussion.