Thanks for your contribution.
However if a timeout is set globally, this usually means there is a reason why requests should time out after the set time. And if file uploads are to be handled differently, I think it's better to explicitly set this in the fileupload initialization, than to set it globally, which might lead to surprises.

Well, normally someone might set the timeout and just have the response time in mind but for timeout the request time counts as well, in this case the length of the whole upload. In my case it was unexpected and I see no reason why anyone would ever want to have a timeout on an upload request.

there is a reason why requests should time out after the set time

Yes, like I wrote in the commit description there are certain Chrome bugs:
https://stackoverflow.com/q/21063909

That is a valid argument. I've reconsidered and the surprise of not following the global timeout setting is a lesser concern, so I'll merge it. Thanks for your patience!

Great, thank you. Also worth mentioning in the wiki (which I can't edit in this repo BTW).

Done. Wiki editing is disabled as it was too much of a hassle to revert spam changes.