On 2015-05-17, Alan Corey <[email protected]> wrote: > I didn't look at what FETCH_CMD was defined as by default, I just assumed > defining something non-null changed it. I did notice that when it retries > it's wrongly assumed there's a problem with the first source and gone to > another.
That's a reasonable supposition because in the majority of cases, it's correct and you do want to move on to another host. It's common to see files which are no longer present return an "error" page with a 200 OK response; when that happens you *have* to move on. > Does every developer have perfect internet? That's very frustrating, maybe > counterproductive in testing. Try a modem, you can probably find a free > one. Connection interruptions and resets happen many times a day. Modem, yeah easy. Dialup ISP not so much. Per-minute connection charges in many cases too. But then back when I was on dialup I didn't get that many interruptions/resets, and when they did happen TCP sessions generally recovered. People tended to use specialist download programs for anything large though, maybe you should too?
