PeerTube/server/middlewares/validators/videos.ts

204 lines
7.4 KiB
TypeScript
Raw Normal View History

2017-06-10 15:15:25 -05:00
import 'express-validator'
import * as multer from 'multer'
import * as express from 'express'
2017-05-22 13:58:25 -05:00
import { database as db } from '../../initializers/database'
2017-05-15 15:22:03 -05:00
import { checkErrors } from './utils'
import { CONSTRAINTS_FIELDS, SEARCHABLE_COLUMNS } from '../../initializers'
import { logger, isVideoDurationValid } from '../../helpers'
2015-11-07 07:16:26 -06:00
2017-06-10 15:15:25 -05:00
function videosAddValidator (req: express.Request, res: express.Response, next: express.NextFunction) {
2017-02-10 04:27:14 -06:00
req.checkBody('videofile', 'Should have a valid file').isVideoFile(req.files)
2016-06-06 07:15:03 -05:00
req.checkBody('name', 'Should have a valid name').isVideoNameValid()
2017-03-22 15:15:55 -05:00
req.checkBody('category', 'Should have a valid category').isVideoCategoryValid()
2017-03-27 13:53:11 -05:00
req.checkBody('licence', 'Should have a valid licence').isVideoLicenceValid()
2017-04-07 05:13:37 -05:00
req.checkBody('language', 'Should have a valid language').optional().isVideoLanguageValid()
2017-03-28 14:19:46 -05:00
req.checkBody('nsfw', 'Should have a valid NSFW attribute').isVideoNSFWValid()
2016-06-06 07:15:03 -05:00
req.checkBody('description', 'Should have a valid description').isVideoDescriptionValid()
req.checkBody('tags', 'Should have correct tags').optional().isVideoTagsValid()
2015-11-07 07:16:26 -06:00
logger.debug('Checking videosAdd parameters', { parameters: req.body, files: req.files })
2015-11-07 07:16:26 -06:00
2016-05-16 12:49:10 -05:00
checkErrors(req, res, function () {
const videoFile = req.files.videofile[0]
2016-12-11 14:50:51 -06:00
db.Video.getDurationFromFile(videoFile.path, function (err, duration) {
2016-05-16 12:49:10 -05:00
if (err) {
return res.status(400).send('Cannot retrieve metadata of the file.')
}
2017-05-15 15:22:03 -05:00
if (!isVideoDurationValid(duration)) {
return res.status(400).send('Duration of the video file is too big (max: ' + CONSTRAINTS_FIELDS.VIDEOS.DURATION.max + 's).')
2016-05-16 12:49:10 -05:00
}
2017-06-10 15:15:25 -05:00
videoFile['duration'] = duration
2016-05-16 12:49:10 -05:00
next()
})
})
}
2015-11-07 07:16:26 -06:00
2017-06-10 15:15:25 -05:00
function videosUpdateValidator (req: express.Request, res: express.Response, next: express.NextFunction) {
2016-12-11 14:50:51 -06:00
req.checkParams('id', 'Should have a valid id').notEmpty().isUUID(4)
2016-12-29 12:07:05 -06:00
req.checkBody('name', 'Should have a valid name').optional().isVideoNameValid()
2017-03-22 15:15:55 -05:00
req.checkBody('category', 'Should have a valid category').optional().isVideoCategoryValid()
2017-03-27 13:53:11 -05:00
req.checkBody('licence', 'Should have a valid licence').optional().isVideoLicenceValid()
2017-04-07 05:13:37 -05:00
req.checkBody('language', 'Should have a valid language').optional().isVideoLanguageValid()
2017-03-28 14:19:46 -05:00
req.checkBody('nsfw', 'Should have a valid NSFW attribute').optional().isVideoNSFWValid()
2016-12-29 12:07:05 -06:00
req.checkBody('description', 'Should have a valid description').optional().isVideoDescriptionValid()
req.checkBody('tags', 'Should have correct tags').optional().isVideoTagsValid()
2015-11-07 07:16:26 -06:00
2016-12-29 12:07:05 -06:00
logger.debug('Checking videosUpdate parameters', { parameters: req.body })
2015-11-07 07:16:26 -06:00
checkErrors(req, res, function () {
2017-01-11 12:15:23 -06:00
checkVideoExists(req.params.id, res, function () {
// We need to make additional checks
if (res.locals.video.isOwned() === false) {
return res.status(403).send('Cannot update video of another pod')
}
2017-01-11 12:15:23 -06:00
if (res.locals.video.Author.userId !== res.locals.oauth.token.User.id) {
return res.status(403).send('Cannot update video of another user')
}
2017-01-11 12:15:23 -06:00
next()
})
2016-12-29 12:07:05 -06:00
})
}
2016-02-04 14:10:33 -06:00
2017-06-10 15:15:25 -05:00
function videosGetValidator (req: express.Request, res: express.Response, next: express.NextFunction) {
2016-12-29 12:07:05 -06:00
req.checkParams('id', 'Should have a valid id').notEmpty().isUUID(4)
2015-11-07 07:16:26 -06:00
2016-12-29 12:07:05 -06:00
logger.debug('Checking videosGet parameters', { parameters: req.params })
checkErrors(req, res, function () {
checkVideoExists(req.params.id, res, next)
})
}
2015-11-07 07:16:26 -06:00
2017-06-10 15:15:25 -05:00
function videosRemoveValidator (req: express.Request, res: express.Response, next: express.NextFunction) {
2016-12-11 14:50:51 -06:00
req.checkParams('id', 'Should have a valid id').notEmpty().isUUID(4)
2015-11-07 07:16:26 -06:00
logger.debug('Checking videosRemove parameters', { parameters: req.params })
2015-11-07 07:16:26 -06:00
checkErrors(req, res, function () {
checkVideoExists(req.params.id, res, function () {
// We need to make additional checks
Add ability for an administrator to remove any video (#61) * Add ability for an admin to remove every video on the pod. * Server: add BlacklistedVideos relation. * Server: Insert in BlacklistedVideos relation upon deletion of a video. * Server: Modify BlacklistedVideos schema to add Pod id information. * Server: Moving insertion of a blacklisted video from the `afterDestroy` hook into the process of deletion of a video. To avoid inserting a video when it is removed on its origin pod. When a video is removed on its origin pod, the `afterDestroy` hook is fire, but no request is made on the delete('/:videoId') interface. Hence, we insert into `BlacklistedVideos` only on request on delete('/:videoId') (if requirements for insertion are met). * Server: Add removeVideoFromBlacklist hook on deletion of a video. We are going to proceed in another way :). We will add a new route : /:videoId/blacklist to blacklist a video. We do not blacklist a video upon its deletion now (to distinguish a video blacklist from a regular video delete) When we blacklist a video, the video remains in the DB, so we don't have any concern about its update. It just doesn't appear in the video list. When we remove a video, we then have to remove it from the blacklist too. We could also remove a video from the blacklist to 'unremove' it and make it appear again in the video list (will be another feature). * Server: Add handler for new route post(/:videoId/blacklist) * Client: Add isBlacklistable method * Client: Update isRemovableBy method. * Client: Move 'Delete video' feature from the video-list to the video-watch module. * Server: Exclude blacklisted videos from the video list * Server: Use findAll() in BlacklistedVideos.list() method * Server: Fix addVideoToBlacklist function. * Client: Add blacklist feature. * Server: Use JavaScript Standard Style. * Server: In checkUserCanDeleteVideo, move the callback call inside the db callback function * Server: Modify BlacklistVideo relation * Server: Modifiy Videos methods. * Server: Add checkVideoIsBlacklistable method * Server: Rewrite addVideoToBlacklist method * Server: Fix checkVideoIsBlacklistable method * Server: Add return to addVideoToBlacklist method
2017-04-26 14:22:10 -05:00
// Check if the user who did the request is able to delete the video
checkUserCanDeleteVideo(res.locals.oauth.token.User.id, res, function () {
next()
})
2015-11-07 07:16:26 -06:00
})
})
}
2015-11-07 07:16:26 -06:00
2017-06-10 15:15:25 -05:00
function videosSearchValidator (req: express.Request, res: express.Response, next: express.NextFunction) {
2017-05-15 15:22:03 -05:00
const searchableColumns = SEARCHABLE_COLUMNS.VIDEOS
2016-06-06 07:15:03 -05:00
req.checkParams('value', 'Should have a valid search').notEmpty()
req.checkQuery('field', 'Should have correct searchable column').optional().isIn(searchableColumns)
2016-01-31 04:23:52 -06:00
logger.debug('Checking videosSearch parameters', { parameters: req.params })
2016-01-31 04:23:52 -06:00
checkErrors(req, res, next)
}
2016-01-31 04:23:52 -06:00
2017-06-10 15:15:25 -05:00
function videoAbuseReportValidator (req: express.Request, res: express.Response, next: express.NextFunction) {
2017-01-04 13:59:23 -06:00
req.checkParams('id', 'Should have a valid id').notEmpty().isUUID(4)
req.checkBody('reason', 'Should have a valid reason').isVideoAbuseReasonValid()
logger.debug('Checking videoAbuseReport parameters', { parameters: req.body })
checkErrors(req, res, function () {
checkVideoExists(req.params.id, res, next)
})
}
2017-06-10 15:15:25 -05:00
function videoRateValidator (req: express.Request, res: express.Response, next: express.NextFunction) {
2017-03-08 14:35:43 -06:00
req.checkParams('id', 'Should have a valid id').notEmpty().isUUID(4)
req.checkBody('rating', 'Should have a valid rate type').isVideoRatingTypeValid()
logger.debug('Checking videoRate parameters', { parameters: req.body })
checkErrors(req, res, function () {
checkVideoExists(req.params.id, res, next)
})
}
2017-06-10 15:15:25 -05:00
function videosBlacklistValidator (req: express.Request, res: express.Response, next: express.NextFunction) {
2017-04-26 14:42:36 -05:00
req.checkParams('id', 'Should have a valid id').notEmpty().isUUID(4)
logger.debug('Checking videosBlacklist parameters', { parameters: req.params })
checkErrors(req, res, function () {
checkVideoExists(req.params.id, res, function () {
checkVideoIsBlacklistable(req, res, next)
})
})
}
// ---------------------------------------------------------------------------
2016-01-31 04:23:52 -06:00
2017-05-15 15:22:03 -05:00
export {
videosAddValidator,
videosUpdateValidator,
videosGetValidator,
videosRemoveValidator,
videosSearchValidator,
videoAbuseReportValidator,
videoRateValidator,
videosBlacklistValidator
}
2016-12-29 12:07:05 -06:00
// ---------------------------------------------------------------------------
2017-06-10 15:15:25 -05:00
function checkVideoExists (id: string, res: express.Response, callback: () => void) {
2016-12-29 12:07:05 -06:00
db.Video.loadAndPopulateAuthorAndPodAndTags(id, function (err, video) {
if (err) {
logger.error('Error in video request validator.', { error: err })
return res.sendStatus(500)
}
if (!video) return res.status(404).send('Video not found')
res.locals.video = video
callback()
})
}
Add ability for an administrator to remove any video (#61) * Add ability for an admin to remove every video on the pod. * Server: add BlacklistedVideos relation. * Server: Insert in BlacklistedVideos relation upon deletion of a video. * Server: Modify BlacklistedVideos schema to add Pod id information. * Server: Moving insertion of a blacklisted video from the `afterDestroy` hook into the process of deletion of a video. To avoid inserting a video when it is removed on its origin pod. When a video is removed on its origin pod, the `afterDestroy` hook is fire, but no request is made on the delete('/:videoId') interface. Hence, we insert into `BlacklistedVideos` only on request on delete('/:videoId') (if requirements for insertion are met). * Server: Add removeVideoFromBlacklist hook on deletion of a video. We are going to proceed in another way :). We will add a new route : /:videoId/blacklist to blacklist a video. We do not blacklist a video upon its deletion now (to distinguish a video blacklist from a regular video delete) When we blacklist a video, the video remains in the DB, so we don't have any concern about its update. It just doesn't appear in the video list. When we remove a video, we then have to remove it from the blacklist too. We could also remove a video from the blacklist to 'unremove' it and make it appear again in the video list (will be another feature). * Server: Add handler for new route post(/:videoId/blacklist) * Client: Add isBlacklistable method * Client: Update isRemovableBy method. * Client: Move 'Delete video' feature from the video-list to the video-watch module. * Server: Exclude blacklisted videos from the video list * Server: Use findAll() in BlacklistedVideos.list() method * Server: Fix addVideoToBlacklist function. * Client: Add blacklist feature. * Server: Use JavaScript Standard Style. * Server: In checkUserCanDeleteVideo, move the callback call inside the db callback function * Server: Modify BlacklistVideo relation * Server: Modifiy Videos methods. * Server: Add checkVideoIsBlacklistable method * Server: Rewrite addVideoToBlacklist method * Server: Fix checkVideoIsBlacklistable method * Server: Add return to addVideoToBlacklist method
2017-04-26 14:22:10 -05:00
2017-06-10 15:15:25 -05:00
function checkUserCanDeleteVideo (userId: number, res: express.Response, callback: () => void) {
Add ability for an administrator to remove any video (#61) * Add ability for an admin to remove every video on the pod. * Server: add BlacklistedVideos relation. * Server: Insert in BlacklistedVideos relation upon deletion of a video. * Server: Modify BlacklistedVideos schema to add Pod id information. * Server: Moving insertion of a blacklisted video from the `afterDestroy` hook into the process of deletion of a video. To avoid inserting a video when it is removed on its origin pod. When a video is removed on its origin pod, the `afterDestroy` hook is fire, but no request is made on the delete('/:videoId') interface. Hence, we insert into `BlacklistedVideos` only on request on delete('/:videoId') (if requirements for insertion are met). * Server: Add removeVideoFromBlacklist hook on deletion of a video. We are going to proceed in another way :). We will add a new route : /:videoId/blacklist to blacklist a video. We do not blacklist a video upon its deletion now (to distinguish a video blacklist from a regular video delete) When we blacklist a video, the video remains in the DB, so we don't have any concern about its update. It just doesn't appear in the video list. When we remove a video, we then have to remove it from the blacklist too. We could also remove a video from the blacklist to 'unremove' it and make it appear again in the video list (will be another feature). * Server: Add handler for new route post(/:videoId/blacklist) * Client: Add isBlacklistable method * Client: Update isRemovableBy method. * Client: Move 'Delete video' feature from the video-list to the video-watch module. * Server: Exclude blacklisted videos from the video list * Server: Use findAll() in BlacklistedVideos.list() method * Server: Fix addVideoToBlacklist function. * Client: Add blacklist feature. * Server: Use JavaScript Standard Style. * Server: In checkUserCanDeleteVideo, move the callback call inside the db callback function * Server: Modify BlacklistVideo relation * Server: Modifiy Videos methods. * Server: Add checkVideoIsBlacklistable method * Server: Rewrite addVideoToBlacklist method * Server: Fix checkVideoIsBlacklistable method * Server: Add return to addVideoToBlacklist method
2017-04-26 14:22:10 -05:00
// Retrieve the user who did the request
db.User.loadById(userId, function (err, user) {
if (err) {
logger.error('Error in video request validator.', { error: err })
return res.sendStatus(500)
}
// Check if the user can delete the video
2017-04-26 14:42:36 -05:00
// The user can delete it if s/he is an admin
// Or if s/he is the video's author
Add ability for an administrator to remove any video (#61) * Add ability for an admin to remove every video on the pod. * Server: add BlacklistedVideos relation. * Server: Insert in BlacklistedVideos relation upon deletion of a video. * Server: Modify BlacklistedVideos schema to add Pod id information. * Server: Moving insertion of a blacklisted video from the `afterDestroy` hook into the process of deletion of a video. To avoid inserting a video when it is removed on its origin pod. When a video is removed on its origin pod, the `afterDestroy` hook is fire, but no request is made on the delete('/:videoId') interface. Hence, we insert into `BlacklistedVideos` only on request on delete('/:videoId') (if requirements for insertion are met). * Server: Add removeVideoFromBlacklist hook on deletion of a video. We are going to proceed in another way :). We will add a new route : /:videoId/blacklist to blacklist a video. We do not blacklist a video upon its deletion now (to distinguish a video blacklist from a regular video delete) When we blacklist a video, the video remains in the DB, so we don't have any concern about its update. It just doesn't appear in the video list. When we remove a video, we then have to remove it from the blacklist too. We could also remove a video from the blacklist to 'unremove' it and make it appear again in the video list (will be another feature). * Server: Add handler for new route post(/:videoId/blacklist) * Client: Add isBlacklistable method * Client: Update isRemovableBy method. * Client: Move 'Delete video' feature from the video-list to the video-watch module. * Server: Exclude blacklisted videos from the video list * Server: Use findAll() in BlacklistedVideos.list() method * Server: Fix addVideoToBlacklist function. * Client: Add blacklist feature. * Server: Use JavaScript Standard Style. * Server: In checkUserCanDeleteVideo, move the callback call inside the db callback function * Server: Modify BlacklistVideo relation * Server: Modifiy Videos methods. * Server: Add checkVideoIsBlacklistable method * Server: Rewrite addVideoToBlacklist method * Server: Fix checkVideoIsBlacklistable method * Server: Add return to addVideoToBlacklist method
2017-04-26 14:22:10 -05:00
if (user.isAdmin() === false) {
if (res.locals.video.isOwned() === false) {
return res.status(403).send('Cannot remove video of another pod')
}
if (res.locals.video.Author.userId !== res.locals.oauth.token.User.id) {
return res.status(403).send('Cannot remove video of another user')
}
}
// If we reach this comment, we can delete the video
callback()
})
}
2017-06-10 15:15:25 -05:00
function checkVideoIsBlacklistable (req: express.Request, res: express.Response, callback: () => void) {
Add ability for an administrator to remove any video (#61) * Add ability for an admin to remove every video on the pod. * Server: add BlacklistedVideos relation. * Server: Insert in BlacklistedVideos relation upon deletion of a video. * Server: Modify BlacklistedVideos schema to add Pod id information. * Server: Moving insertion of a blacklisted video from the `afterDestroy` hook into the process of deletion of a video. To avoid inserting a video when it is removed on its origin pod. When a video is removed on its origin pod, the `afterDestroy` hook is fire, but no request is made on the delete('/:videoId') interface. Hence, we insert into `BlacklistedVideos` only on request on delete('/:videoId') (if requirements for insertion are met). * Server: Add removeVideoFromBlacklist hook on deletion of a video. We are going to proceed in another way :). We will add a new route : /:videoId/blacklist to blacklist a video. We do not blacklist a video upon its deletion now (to distinguish a video blacklist from a regular video delete) When we blacklist a video, the video remains in the DB, so we don't have any concern about its update. It just doesn't appear in the video list. When we remove a video, we then have to remove it from the blacklist too. We could also remove a video from the blacklist to 'unremove' it and make it appear again in the video list (will be another feature). * Server: Add handler for new route post(/:videoId/blacklist) * Client: Add isBlacklistable method * Client: Update isRemovableBy method. * Client: Move 'Delete video' feature from the video-list to the video-watch module. * Server: Exclude blacklisted videos from the video list * Server: Use findAll() in BlacklistedVideos.list() method * Server: Fix addVideoToBlacklist function. * Client: Add blacklist feature. * Server: Use JavaScript Standard Style. * Server: In checkUserCanDeleteVideo, move the callback call inside the db callback function * Server: Modify BlacklistVideo relation * Server: Modifiy Videos methods. * Server: Add checkVideoIsBlacklistable method * Server: Rewrite addVideoToBlacklist method * Server: Fix checkVideoIsBlacklistable method * Server: Add return to addVideoToBlacklist method
2017-04-26 14:22:10 -05:00
if (res.locals.video.isOwned() === true) {
2017-04-26 14:42:36 -05:00
return res.status(403).send('Cannot blacklist a local video')
Add ability for an administrator to remove any video (#61) * Add ability for an admin to remove every video on the pod. * Server: add BlacklistedVideos relation. * Server: Insert in BlacklistedVideos relation upon deletion of a video. * Server: Modify BlacklistedVideos schema to add Pod id information. * Server: Moving insertion of a blacklisted video from the `afterDestroy` hook into the process of deletion of a video. To avoid inserting a video when it is removed on its origin pod. When a video is removed on its origin pod, the `afterDestroy` hook is fire, but no request is made on the delete('/:videoId') interface. Hence, we insert into `BlacklistedVideos` only on request on delete('/:videoId') (if requirements for insertion are met). * Server: Add removeVideoFromBlacklist hook on deletion of a video. We are going to proceed in another way :). We will add a new route : /:videoId/blacklist to blacklist a video. We do not blacklist a video upon its deletion now (to distinguish a video blacklist from a regular video delete) When we blacklist a video, the video remains in the DB, so we don't have any concern about its update. It just doesn't appear in the video list. When we remove a video, we then have to remove it from the blacklist too. We could also remove a video from the blacklist to 'unremove' it and make it appear again in the video list (will be another feature). * Server: Add handler for new route post(/:videoId/blacklist) * Client: Add isBlacklistable method * Client: Update isRemovableBy method. * Client: Move 'Delete video' feature from the video-list to the video-watch module. * Server: Exclude blacklisted videos from the video list * Server: Use findAll() in BlacklistedVideos.list() method * Server: Fix addVideoToBlacklist function. * Client: Add blacklist feature. * Server: Use JavaScript Standard Style. * Server: In checkUserCanDeleteVideo, move the callback call inside the db callback function * Server: Modify BlacklistVideo relation * Server: Modifiy Videos methods. * Server: Add checkVideoIsBlacklistable method * Server: Rewrite addVideoToBlacklist method * Server: Fix checkVideoIsBlacklistable method * Server: Add return to addVideoToBlacklist method
2017-04-26 14:22:10 -05:00
}
callback()
}