As a concrete example where wget's HTTP/1.0 header causes an issue, I'm evaluating a Juniper DX web cache, and it is sending a different response to wget than to a browser, thanks to the HTTP/1.0 query. (When I sent the original email I hadn't confirmed this was true, it is.)
I think this is actually a bug in Juniper's software, and have reported it to Juniper, but, it should be no surprise that acting different from 99% of web queries (which are 1.1) can cause problems for wget users. -- greg
