Fix for querystring being incorrectly appended if querystring already exists, and handle null response from server #5

merged 2 commits into from Oct 3, 2012

2 participants


If the form action already contains a querystring uploadProgress would append a second question mark followed by the X-Progress-ID, this patch handles this situation correctly and uses an ampersand instead if so.

Also if the server returns with a null or false response, which happens in several situations which use caching intermediaries for signalling upload status when out of the upload process, I've added a patch to just assume this is the end of upload (you can't assume an actual error as there's no other data to go on, an alternative to this might be the pass the XHR object and check for a 50x status header, but I don't need to do this so haven't).

1stvamp added some commits Jul 17, 2011
@1stvamp 1stvamp Check for server response being null if testing locally (processed to…
…o quickly), and correctly append X-Progress-ID with ampersand when there's already a querystring.
@1stvamp 1stvamp Assume false response from server means we've gone past the upload pr…

Bump, /cc @drogus


@1stvamp sorry for delaying it for so long, I think I haven't got the previous notifications due to filters set for github emails - now when github made their notifications system better it came to my main inbox

@drogus drogus merged commit 35b3000 into drogus:master Oct 3, 2012

@drogus no problem! I had the exact same issues with a bunch of pull requests until recently, just decided to go through my pending PR list every month or so to ping people or respond to people asking me for pulls. Cheers :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment