2G limit on creating media
Closed this issue · 3 comments
GoogleCodeExporter commented
What steps will reproduce the problem?
1. try to POST a media resource 2G or greater to a collection
What is the expected output? What do you see instead?
Expect it to work, instead see 0 length in media-link entry
Original issue reported on code.google.com by alimanfoo@googlemail.com on 1 Mar 2011 at 6:06
GoogleCodeExporter commented
this is due to request.getContentLength() returning an int; atombeat needs to
access the content-length request header directly and parse as a long
Original comment by alimanfoo@googlemail.com on 1 Mar 2011 at 6:07
GoogleCodeExporter commented
fixed in rev 635
Original comment by alimanfoo@googlemail.com on 1 Mar 2011 at 6:19
- Changed state: Fixed
GoogleCodeExporter commented
Original comment by alimanfoo@googlemail.com on 8 Mar 2011 at 3:08