Except for some CMS or Blogging machines that are "shared"...

Only if you are on something like "www.blogthis.info/yourblog" the sitemap for your "sub site" would be "www.blogthis.info/yourblog/sitemap.xml"

If they request a sitemap somewhere other than proper placement, they are either fishing for badly configured sites, or deliberately trying to probe you for what exactly you have setup and where things are...

Typically, this works on Window IIS server because of all the automagic stuff they do, but in all honesty, do you really want to support "Windows" nomenclature and functions on non-IIS servers?

In all honesty, you can add in all the "corrections for errors" you want, you are just feeding evidence for this stuff by rote and not with good reasoning.

If you really want to support this kind of stuff, you should look into the "mod spelling" module for Apache and get into using that properly. It'll help people much more than these 5000 rules from an SEO will. But mod_speling will definitely have an impact on performance if you get scanned/scraped with bad stuff trying to find your "myphpadmin" (just an example) pages.

Its a juggle, all of these "protections" from the user getting lost sometimes make managing things just not worth the time and effort. You'd think with all these really new and fully featured Web Browsers existing now a days, this stuff would just go away. But again, advice from 12 years ago on how to push all the wonky stuff that existed back then (including the drive away from ".gif") to a standard today...

Think about how many people still use the browsers from 1999... not many, including people still on Windows 95/98/ME and WindowsNT4 and Windows2000. As is the case, in order to even get around the internet now... you have to have a browser that support many newer standards that weren't even thought of yet in 1999.

Take my opinion with a Grain of salt and let it simmer a bit. Then do what you want.