"it gets to about 99% then gives me an http error" - this does sound like some kind of error on your client or server. However if you individually report the HTTP error and can send a screencast going through the browser's network inspector to look at all the response details for the upload AKAX request, I could take a look. You'd need to open the inspector before you start the upload, and show all the headers and the full response data.
This is a combination of a couple of subtle bugs, and misunderstandings.
"The filesize wasn't detected"
Code assumed allow_url_fopen PHP option was on even though we explicitly turn it off. I've re-implemented detection is a safe-way, using our own downloader.
"and seems to revert to 16k"
I think 1.6GB actually. And that's actually due to a bug, this is basically a random number we use for inline editing detection. Fixed.
"The filesize is being shown at 107KB though"
The option is in bytes, not KB - so this is a misunderstanding.
Oh, bytes. That explains the confusion here and I didn't see bytes in your previous reply (read it as kilobytes). Guess I need to google how many bytes are in 109398kb then.
I can deal with the rest though.
"The filesize wasn't detected"
Code assumed allow_url_fopen PHP option was on even though we explicitly turn it off. I've re-implemented detection is a safe-way, using our own downloader.
"and seems to revert to 16k"
I think 1.6GB actually. And that's actually due to a bug, this is basically a random number we use for inline editing detection. Fixed.
"The filesize is being shown at 107KB though"
The option is in bytes, not KB - so this is a misunderstanding.