You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I like the idea of uploading directly to the storage service instead of the data passing through my server.
However, this way, we have to give control to the user to tell us what the download url actually is.
E.g. from the readme:
varuploader=newSlingshot.Upload("myFileUploads");uploader.send(document.getElementById('input').files[0],function(error,downloadUrl){if(error){// Log service detailed response.console.error('Error uploading',uploader.xhr.response);alert(error);}else{Meteor.users.update(Meteor.userId(),{$push: {"profile.files": downloadUrl}});}});
So the user could enter any URL, even if what is at that URL does not abide by our validation rules for the directive. Which, depending on what you do with the resulting url, might be dangerous.
Is there any way for example to let S3 ping our server when an upload is done, by incorporating a 'notify-on-upload-complete url' in the directive (just making something up here) ?
The text was updated successfully, but these errors were encountered:
I like the idea of uploading directly to the storage service instead of the data passing through my server.
However, this way, we have to give control to the user to tell us what the download url actually is.
E.g. from the readme:
So the user could enter any URL, even if what is at that URL does not abide by our validation rules for the directive. Which, depending on what you do with the resulting url, might be dangerous.
Is there any way for example to let S3 ping our server when an upload is done, by incorporating a 'notify-on-upload-complete url' in the directive (just making something up here) ?
The text was updated successfully, but these errors were encountered: