4 ms·
> What's wrong with "www."? People (rightly) expect the url to work without it. I say rightly, because it can, so it should. The www hads no value to the user.
by norswap 13y ago
> What's wrong with "www."?
People (rightly) expect the url to work without it. I say rightly, because it can, so it should. The www hads no value to the user.
- JoachimSchipper 13y agoThat's an extremely web-centric view of the world. There is more to DNS than its use in URLs. And doesn't redirecting to www. do the expected thing anyway?
- Xylakant 13y agoTo redirect to www.example.org I need a server listening at example.org. If I have www.example.org on heroku because I don't want to run a server, I suddenly need a server just for that redirect that I need to have because I don't want to run a server.
- JoachimSchipper 13y agoBut there's already a non-Heroku server running for that domain, i.e. the one serving DNS requests. That server can be re-purposed to do HTTP-level redirects, too, and indeed many name server operators offer that feature.
- zimbatm 13y agoOr just use http://wwwizer.com/ http://wwwizer.com/ EDIT: Or use DNSMadeEasy, they provide HTTP redirect options as part of their service (although I wish the default option would not be to wrap the target URL in an iframe...)
- toomuchtodo 13y agoOr use an S3 bucket with a redirect.
- norswap 13y agoIt does, but then can you do that without using an ALIAS record, which is one of the reason invoked to use "www"? Also, web-centric is fine, browsing the net is 99% of my URL manipulation, and I'm a developer that has to work with web APIs.