Is it safe to use http(s)://CompanyName.com/xyz as URL (e.g. for branding purposes) without any changes to the service-side configs?
I know that DNS is case-insensitive, but could there still be side-effects? I am thinking of e.g. various parts of the chain failing to match CompanyName.com ~ companyname.com:
- Some web backend might fail to match
- Some load balancer/proxy/cache/application layer firewall might fail to match
- Some client might apply same-origin policies wrongly
- Some client might fail to match in certificate checks
- While DNS is generally case-insensitive, could IDNs change the picture?
Anyone experienced those or other issues with capitals in the hostname part of URLs?
 @Michael Hampton pointed out that, according the the HTTP standards, the hostname IS case-insensitive, but some software is non-compliant in this regard.
I try to get a sense of how prevalent non-compliant software is, in particular clients. I assume all recent major browsers are fine, but what e.g. about mobile apps? (Should I better split this off into a separate SF question?) [/edit]