camelcased domains should be lowercased or produce an error

[Mouvedia]

I entered a domain camelcased and didn't receive any error. It seems you are considering "exAmple" and "example" to be 2 different domains.

Obviously, our typical surge user wouldn't make the assumption that domains are case sensitive in the first place.

[MaxLaumeister]

I ran into this issue today. It looked like the site uploaded to the camel case domain, but then when I went to visit it, I was redirected to the lowercase domain and got a 404. I went to tear down the camel case version, and surge teardown said "Aborted - unable to remove [lowercase].surge.sh".

Looks like that camel cased revision is somewhere in the ether now - but from now on I'm going to use lowercase domains!

[maxkwallace]

I ran into this same issue yesterday. I also sent an email about it to 'info' at chloi.io with the subject line "Issues with non-autogenerated names?" I'd really like to be able to teardown those inaccessible domains, rather than just leave them hanging-- they still appear in surge list.

[huwd]

Also discussed over here: #230