1 November 2005 1 comment This site
This blog post is 17 years old! Most likely, its content is outdated. Especially if it's technical.
I've now set up alias to www.peterbe.com such that ww.peterbe.com and wwww.peterbe.com both redirect to www.peterbe.com.
We'll see what effect this might have and if it's worth. I guess 99% of all visitors on this site get it right but this tightens the "fool-proofness" even more. Google have one such alias set up on ww.google.com but not wwww.google.com
- Previous:
- Using MD5 to check equality between files 28 October 2005
- Next:
- Whitelist blacklist logic 2 November 2005
- Related by category:
- Aggressively prefetching everything you might click 20 August 2014 This site
- What makes my website slow? DNS 23 October 2009 This site
- Wattvision - real-time energy monitoring 27 April 2014 This site
- 10 years of blogging 19 September 2013 This site
- PlogRank - my own PageRank application 21 May 2004 This site
- Related by keyword:
- How to use letsencrypt-acme-challenge.conf in Nginx 5 September 2021
- The correct way to index data into Elasticsearch with (Python) elasticsearch-dsl 14 May 2021
- How to unset aliases set by Oh My Zsh 14 June 2018
- redirect-chain - Getting a comfortable insight input URL redirects history 14 February 2020
- How I found out where a bash alias was set up 9 May 2018
Another options: Put in a catchall, so even typing vvv.peterbe.com (or isurecannnottype.peterbe.com) will get it right :-) This does not get in the way of using more meaningfull subdomains for other purposes.