I've learned that there is definitely a 10MB upload limit through
heroku,
and the expectation is that if you're uploading big files to S3 you
use
a direct upload method.
If anyone has had success with easy clean integration of a direct
upload method
please do share!
Thanks,
Martin.
On Apr
I got it while trying to do an upload of a 20M file using WebKit (the
413 Request Entity Too Large error that is) and the Connection
Interrupted error i got while using firefox.
On Apr 14, 5:17 am, GreenAsJade martin.jg.greg...@gmail.com wrote:
Dang, I've got this sort of problem now too.
Any more progress on this?
Is it actually a heroku-induced limit, or something else?
On Apr 14, 4:53 pm, Robert Sköld slas...@gmail.com wrote:
I got it while trying to do an upload of a 20M file using WebKit (the
413 Request Entity Too Large error that is) and the Connection
Interrupted
Dang, I've got this sort of problem now too.
Users reporting timeouts on uploads to S3 via heroku of files
larger than 10M
9M : OK
10M: not OK.
Where did you get the error message: I haven't even got as far as
finding anything
telling me what's behind this.
Martin
Hey there,
I'm using your heroku service (not herokugarden) and when i'm trying
to upload a file that's 20Mb or 10Mb through heroku to my S3 storage,
using firefox, it tells me:
Connection Interrupted
The connection to the server was reset while the page was loading.
The network link was
Is your connection to S3 set up as persistent (the default)?
I read:
* :persistent - Whether to use a persistent connection to the
server. Having this on provides around a two fold performance increase
but for long running processes some firewalls may find the long lived
connection
Thanks for you answer, i've tried changing my amazon connection to:
AWS::S3::Base.establish_connection!( :access_key_id =
Settings[:amazon_key], :secret_access_key =
Settings[:amazon_secret] , :persistent = false )
and it doesn't seem to make any difference unfortunately. It's after
about
