Isn't the expected behavior simply that wget behaves as normal but saves the file to the extension specified by the mime type in content-disposition? Why does this result in performance issues? I have encountered this same issue with my web app. You have to specify -OfileNameYouExpect, which is what I think users expect wget to do for them.
- Re: [Bug-wget] Output filename not same as from browser save.... Brian
