Comment
Comment by JackC
The author mentions a mitigation of specifying a filename in the Content-Disposition header, which that particular url actually does:
Perhaps Google has fixed the problem for that URL -- I would hope the author contacted them in advance.