Skip to content
This repository has been archived by the owner on Nov 9, 2024. It is now read-only.

Wrting to blob storage fails with a 413 (request body maximum size limit was exceeded) #23

Open
24X7 opened this issue Jun 9, 2014 · 4 comments

Comments

@24X7
Copy link

24X7 commented Jun 9, 2014

Scenario:

  1. Take a picture with iPad Air
  2. Upload picture from iPad through an HTML form post to an Azure Mobile Service API
  3. Error returns (413) due to size of the request. Debugged, and it is being thrown at the bottom lines in my implementation

Relevant usage code:
//container varaible below is bluesky container for blobs
var readStream = fs.createReadStream(request.files.snapshot.path);
readStream.pipe(container.put(corid)); //errors with the 413 on this line
response.send(200, {msg: 'photo uploaded'});

If this is by design in anyway and I am just using this wrong LMK or if there is something more that may be helpful I can provide.

@pofallon
Copy link
Owner

pofallon commented Jun 9, 2014

Any idea the size of the image that's generating the error? Also, is this a sporadic error, or do you see it every time?

@24X7
Copy link
Author

24X7 commented Jun 9, 2014

See it every time. I can get the exact size shortly. Essentially it happens to any image taken with the back camera on iPad Air / iPhone 5s. Front facing camera does not cause the issue. I know the data needs to be chunked in blocks to be uploaded for larger post data (thought though was 64mb).

Sent from my iPad

On Jun 8, 2014, at 6:45 PM, "pofallon" [email protected] wrote:

Any idea the size of the image that's generating the error? Also, is this a sporadic error, or do you see it every time?


Reply to this email directly or view it on GitHub.

@24X7
Copy link
Author

24X7 commented Jun 9, 2014

Here is one of the images I took with the rear facing camera. Funny, it actually happens every single time. Was able to repro with other images as well.

image

@24X7
Copy link
Author

24X7 commented Jun 9, 2014

It is 1.09MB. Seems to hit an issue when going over a 1MB. I looked at your code and did not see an issue off hand; but will debug more and see if I can find it.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants