Allowed crossdomain for Parse.file upload with POST #169
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix for #118
Allowed crossdomain for the route
POST /files/:filename
This works when uploading a file with Base64 and byte. How ever it doesn't work when uploading with Content-Type image/png
Works
var base64 = "V29ya2luZyBhdCBQYXJzZSBpcyBncmVhdCE=";
var file = new Parse.File("myfile.txt", { base64: base64 });
file.save();
Works
var bytes = [ 0xBE, 0xEF, 0xCA, 0xFE ];
var file = new Parse.File("myfile.txt", bytes);
file.save();
Doesn't work
var file = new Parse.File("myfile.zzz", fileData, "image/png");
file.save();
Reason
When uploading an image with the Content-Type image options request is made
OPTIONS /files/:filename
Note: I haven't used the middlewares.allowCrossDomain method. Please review my code before merge