Is Godaddy naked domain forwarding broken when you have a ./ in the URL?
I use GoDaddy for DNS and have naked domain forwarding setup. I have my A record @ set to GoDaddy servers, and use their interface to forward all naked domain traffic to www.. This works fine in almost all circumstances, such as:
- Working:
example.com --> www.example.com - Working:
example.com/foo --> www.example.com/foo - Working:
example.com/123/foo --> www.example.com/123/foo - Working:
example.com/.foo/ --> www.example.com/.foo/
However, when I use a period and then a slash in the naked domain name, forwarding does not work:
- Broken:
example.com/foo./
Notice that the last working example above differs with the broken example only by the placement of the period.
When I go to the broken URL, instead of being forwarded to the www. page, I get the error message depicted in the screenshot below. This is an aspx .net error message. None of my servers use aspx or .net, so I know that this request has not even hit my server. Is this a bug with GoDaddy forwarding?
