11–20 of 194 posts
This is extremely annoying for a project I'm working on that involves subdomains. If I set nginx to redirect `example.com` to `www.example.com` I want to verify it in the browser.
my chrome hasn't updated yet, but my understanding of this change was that you could display the full unmolested URL by simply clicking in the address bar. is that not the case?
I'm certainly not a fan of the new URI scheme, but it is worth pointing out that Safari has already made the same change. Furthermore I'm not convinced said change is a net-negative for the average consumer. Safari added the setting "Show full website address", which does just that. I wouldn't have a problem if Chrome followed suit and defaulted to the new scheme, but gave us the option to show the full URI.
I don't know if there are any scenarios in which a properly-configured website (mine isn't) needs to differentiate example.com from www.example.com. But I liked the ability to do so easily.
I absolutely do not want it to hide any URI schemes or subdomains at all. (I am able to change these settings in Firefox, at least. I could also disable Unicode rendering for the domain name, but to disable Unicode rendering for the filename I had to write an extension.)
I'm certainly not a fan of the new URI scheme, but it is worth pointing out that Safari has already made the same change. Furthermore I'm not convinced said change is a net-negative for the average consumer. Safari added the setting "Show full website address", which does just that. I wouldn't have a problem if Chrome followed suit and defaulted to the new scheme, but gave us the option to show the full URI.
If I have one webpage with different languages and want my visitors recognize it from url, what are the options? Previously I could have www.example.com/en/ and www.example.com/fr/ etc If subdomains are not possible there's no hope that visitors using Chrome would see it?
URLs represent and identify content,controling them means you control content. In the short term these changes mean little but in the long term this will benefit google immensely. Google just loves slippery slopes. Identity and payment are extremely important to any ordered system of social interaction. More than content itself,controlling them helps one control everything else. I am trying hard to avoid believing co…
google-payments-secure.via.net is not a google payment website despite the google in the domain name. The key part that signifies the ownership / identify of the person hosting the site is the END of the domain, the google.com part. That is the owner of the web property, not whatever appears before that.
If I have one webpage with different languages and want my visitors recognize it from url, what are the options? Previously I could have www.example.com/en/ and www.example.com/fr/ etc If subdomains are not possible there's no hope that visitors using Chrome would see it?
If I have one webpage with different languages and want my visitors recognize it from url, what are the options? Previously I could have www.example.com/en/ and www.example.com/fr/ etc If subdomains are not possible there's no hope that visitors using Chrome would see it?