FIX: Changed Content Type From Static mp4 To Input
Build, Push and Deploy CMS / build-push-deploy (push) Successful in 2m18s
Build, Push and Deploy CMS / build-push-deploy (push) Successful in 2m18s
This commit is contained in:
@@ -44,6 +44,9 @@ definitions:
|
||||
handlers.presignRequest:
|
||||
properties:
|
||||
contentType:
|
||||
enum:
|
||||
- video/mp4
|
||||
- video/quicktime
|
||||
example: video/quicktime
|
||||
type: string
|
||||
fileName:
|
||||
@@ -190,12 +193,13 @@ paths:
|
||||
- application/json
|
||||
description: Step 1 of the upload flow. Returns a short-lived presigned S3 URL
|
||||
that the client PUTs the video file to directly, plus the storage key identifying
|
||||
it. Once the PUT succeeds, pass that same key to POST /api/videos to register
|
||||
the video and start transcoding. The file itself never passes through this
|
||||
API.
|
||||
it. The submitted contentType is signed into that URL, so the PUT must carry
|
||||
an identical Content-Type header or S3 rejects it as a signature mismatch.
|
||||
Once the PUT succeeds, pass the key to POST /api/videos to register the video
|
||||
and start transcoding. The file itself never passes through this API.
|
||||
parameters:
|
||||
- description: Name and media type of the file to be uploaded. contentType must
|
||||
be a video/* type.
|
||||
be exactly 'video/mp4' or 'video/quicktime'.
|
||||
in: body
|
||||
name: request
|
||||
required: true
|
||||
@@ -213,7 +217,7 @@ paths:
|
||||
schema:
|
||||
$ref: '#/definitions/handlers.problemDetails'
|
||||
"422":
|
||||
description: contentType was not a video/* media type
|
||||
description: contentType was not 'video/mp4' or 'video/quicktime'
|
||||
schema:
|
||||
$ref: '#/definitions/handlers.problemDetails'
|
||||
"500":
|
||||
|
||||
Reference in New Issue
Block a user