title: What are the general rules for getting the 104 "Connection reset by peer" error?
body: <p>Are there any general rules on when a website sends out a TCP reset, triggering the <code>Connection reset by peer</code> error?</p>
  
  <p>Like</p>
  
  <ul>
  <li>too many open connections</li>
  <li>too high bandwidth use</li>
  <li>connected for too long</li>
  <li>…?</li>
  </ul>
  
  <p>I'm pretty certain that there is no law governing this and that different websites/web developers have different tastes, but I would be interested if there are some general rule sets (from websites or textbooks on the subject or what you have been taught in school/at work) that are mostly followed.</p>
  
  <p>Reason why I'm asking, of course, is that I want to get around being blocked… </p>
  
  <p><em>I'm downloading some government data that is freely available, but is lacking an API or something, so the two official ways to get it are either clicking around in some web-GIS a few thousand times or going along the Kafkaesque path of explaining various levels of clerks the concepts of databases, csv files, zip files and that you can't (and won't need to, if they'd just did what you try to explain them) just drive to their agency with a "giant" harddrive, so I'm trying to just go the most resource saving way for everyone involved…</em></p>