Mega, Kim Dotcom's, of MegaUpload fame, latest venture, is live and has proved quite popular or at least interesting. It's gotten up to 500,000 registered users in 14 hours and probably ticked the 1 million registered users mark by now.
All this attention is proving too much for the infrastructure which is struggling under the strain.
All this attention is proving too much for the infrastructure which is struggling under the strain.
I have been having trouble with down loads, they all stop at 99% and will not complete the down. If you download a music file, do you use IE8 or Chrome also?
Downloads stuck at 99% No matter what type of file I try to download, IE8 gets stuck at 99% and never finishes the download. I have tried txt, pdf, zip, rar, jpg and mp3. Download stuck at 0.0 KB/s with no resume The status indicates that it is still downloading but I have literally let it go days without it resuming (pretty sad, eh?). I can connect to the same location and download a concurrent copy of the file but if I cancel the download it will not resume even if I restart the download of the same file on. May 14, 2018 - In-depth comparison chart of MEGA vs Dropbox vs Google Drive vs SpiderOak vs SugarSync vs OneDrive and more! Free for users who download Quick Office and other mobile phone deals. Starts from $ 199 per month for 100 GB. All you have to do is go to OneDrive.com in Chrome, log in, open.
The site itself is working, most of the time, but upload/download speeds aren't great if they work at all. Still, it's easy to get an idea of how the site works.
One of the first things that greet you once you complete the registration process is a warning/notification that you're best suited with Google Chrome.
In fact, Mega makes it very clear that Chrome is the only browser supported and strongly encourages you to switch to it. Normally, these warnings are there just so a site can't be held responsible if things go wrong.
In this case, though, you really should be using Chrome. The site works in Firefox for example, but it's noticeably slower.
There are also weird bugs, which are easily explained by the lack of any testing, such as being very hard to tick checkboxes, most of the time your clicks won't be registered, you have to click at just the right spot for it to work.
But it goes deeper than this, there is a reason why Mega has these obvious bugs in Firefox, it was designed for Chrome from the get go since Firefox didn't offer some advanced HTML5 file management features, nor did any other major browser.
In fact, Mega explained exactly why it chose Chrome and why none of the other browsers fit the bill. Here's Mega's explanation in full:
'Google Chrome: The leading browser, by far. It implements the proposed HTML5 FileSystem API, allowing for fancy features such as recursive folder uploads and efficient downloads. Caveats: Requires user permission to batch-write files after a few unattended completed downloads (for security reasons, and only once per session). Slightly anaemic text rendering.
Internet Explorer 10: A solid, modern browser with blazing JavaScript performance (even exceeding Chrome's). However, until Microsoft fixes a memory leak in the Blob saving functionality, you have to close and reopen the MEGA tab every couple of hundred megabytes of inbound file transfer. And, until Microsoft implements disk-based Blobs or Chrome's FileWriter API, memory usage for a file download peaks at twice the file's size - hardly efficient.
Mozilla Firefox 18: Carefully avoids providing any API that would allow writing files from JavaScript.
Safari 6: No JavaScript file writing, either.
Internet Explorer 9: Lacks all essential features required for MEGA: File I/O, Web Workers, ArrayBuffers, and binary cross-domain HTTP access. Nice text rendering, though.
Opera: No JavaScript file writing and exceedingly slow JavaScript crypto operations.'
On a page of a website we're building http://ovsd.nutrislice.com/wellness/ , pdf download links ('Download the Issue') get stuck while loading in Chrome's PDF Viewer but work in all other browsers by triggering a download. Right click + 'Save as' works in Chrome. I realize Chrome is the only browser with a built-in, default pdf viewer.
I figure we can instruct people to right click and then 'save as', but I wanted to see if anyone can see a problem with either the html, or in the server response, which would cause chrome to fail like that.
Its not a traditional pass-thru file download sitting on a server somewhere. We use Heroku, and I'm currently storing the pdf's in the DB (I realize the downsides of this, but it was a simpler system than managing off-site files on S3 for now). I'm generating the response dynamically via a Django View, so I wonder if there's something i'm missing in the response headers or something.
Ben Roberts
Ben RobertsBen Roberts
2 Answers
Looks like a bad content-type:
Check your code where you are assigning a content-type to the response. Looks like you're sending a tuple instead of just
application/pdf
.dgeldgel
Like @dgel mentioned, your content type is incorrect:
Also it might be a good idea to add
Content-Length
header.miki725miki725