[bug #57413] No data detection, recursive mode won; t work if received HTTP responses are always comming in gzip compression

Follow-up Comment #4, bug #57413 (project wget): Tim, have you tried to reproduce on "1.19.5" (Current version I have, this is the version that is actually installed using "yum install wget" and I have no idea how to upgrade to 1.20) I've tried to use --compression flag as you've mentioned with "

[bug #57413] No data detection, recursive mode won; t work if received HTTP responses are always comming in gzip compression

Follow-up Comment #5, bug #57413 (project wget): Hi zahlabut, leave away -i, because it consumes '-r' as a file name and thus wget doesn't work recusively. I just used your command below without '-i' and it seems to work (downloading plenty files). __

[bug #57413] No data detection, recursive mode won; t work if received HTTP responses are always comming in gzip compression

Follow-up Comment #6, bug #57413 (project wget): Hi Tim! Ok, it did work for me without adding -i flag Thanks! ___ Reply to this item at: ___ Message

[bug #54126] Wget keeps crashing in Windows sometimes when the filename is large enough to scroll it

Follow-up Comment #7, bug #54126 (project wget): Sorry, I am not sure what your point is. You say "when USE_NLS_PROGRESS_BAR defined all works fine". But no, not at all. All those changes to prevent different types of buffer and integer overflow have *only* been tested with USE_NLS_PROGRESS_BAR

[SOLVED] RE: Wget with Download directory containing spaces

Hi, I received several suggestions, but no real solution for the issue has surfaced. Apparently, the average Wget user is wise, and makes sure not the use directory names with spaces, so nobody really seems to know how to implement such names when needed. In DOS (Win7, x64) the following co