3 ms·

Not showing complete URLs and de-emphasizing URLs are not good ideas. Safari's way of doing things is terrible. Chrome hides the HTTP and chops off trailing sla

Not showing complete URLs and de-emphasizing URLs are not good ideas. Safari's way of doing things is terrible. Chrome hides the HTTP and chops off trailing slashes. Firefox puts the <title> text before the URLs in the completion dropdown now and it's easier for malicious sites to trick users that way. The URL is not https://www.tesla.com https://www.tesla.com it's https://www.tesla.com/ https://www.tesla.com/. Instead of treating users like they are stupid, educate them. Show them the entire URL and teach them how the WWW works. People are going to encounter URLs anyway (when pasted), so trying to hide their structure is just going to keep making things worse.

slaymaker1907 9y ago
What's wrong with the first one? It seems perfectly legimate since you can use them interchangeably.
- paulddraper 9y ago
  It's not a syntactically incomplete HTTP URL..I didn't come up with the syntax; I just use it.
- JoshMnem 9y ago
  The first one is not the real URL that you're visiting. Go to Firefox and turn off URL trimming or open the browser console and type window.location.pathname. The server will add the trailing slash, but the browser will pretend that it isn't there. Or go to http://example.com#123 http://example.com#123 or http://example.com?123 http://example.com?123 and see where you end up. It makes things more confusing, by hiding what is really going on. It leads to things like otherwise technically-savvy people leaving off trailing slashes on longer pathnames, which can cause other problems. For example, http://example.com/some-path http://example.com/some-path can be much different than http://example.com/some-path/ http://example.com/some-path/ Some browsers were also hiding trailing slashes on longer pathnames, which seems to have stopped (possibly due to breaking sites). By hiding the real URLs, even programmers get confused, not just the end users.
chrismcb 9y ago
Https://www.tesla.com is a different url than https://www.tesla.com/ https://www.tesla.com/ They point to different resources. Of course most people treat these two URLs as the same, but they don't have to be.
- majewsky 9y ago
  Do they? They're both retrieved by issuing the same HTTP request: GET / HTTP/1.1 Host: www.tesla.com You cannot leave the path after the method empty in HTTP.
  - chrismcb 9y ago
    They are both retrieved because the server handles it. Of course you can leave the path empty. From the RFC: > path = path-abempty ; begins with "/" or is empty A better way to look at it is how w3.org defines it: > h t t p : / / hostport [ / path ] [ ? search ] > path : Void | segment [ / path ] Notice how the slash is in the optional part.
    - JoshMnem 9y ago
      I've never seen a site that doesn't serve a root path. You can't serve a homepage at http://example.comindex.html http://example.comindex.html. I'd be curious to see if it's possible to serve one at http://example.com?page=home http://example.com?page=home, http://example.com#home http://example.com#home, or something like that though. In any case, http://www.tesla.com http://www.tesla.com is not the URL of their home page -- it's http://www.tesla.com/ http://www.tesla.com/ even though the browser tries to tell you that you're visiting http://www.tesla.com http://www.tesla.com.

slaymaker1907 9y ago

What's wrong with the first one? It seems perfectly legimate since you can use them interchangeably.

paulddraper 9y ago
It's not a syntactically incomplete HTTP URL..I didn't come up with the syntax; I just use it.
JoshMnem 9y ago
The first one is not the real URL that you're visiting. Go to Firefox and turn off URL trimming or open the browser console and type window.location.pathname. The server will add the trailing slash, but the browser will pretend that it isn't there. Or go to http://example.com#123 http://example.com#123 or http://example.com?123 http://example.com?123 and see where you end up. It makes things more confusing, by hiding what is really going on. It leads to things like otherwise technically-savvy people leaving off trailing slashes on longer pathnames, which can cause other problems. For example, http://example.com/some-path http://example.com/some-path can be much different than http://example.com/some-path/ http://example.com/some-path/ Some browsers were also hiding trailing slashes on longer pathnames, which seems to have stopped (possibly due to breaking sites). By hiding the real URLs, even programmers get confused, not just the end users.

chrismcb 9y ago

Https://www.tesla.com is a different url than https://www.tesla.com/ https://www.tesla.com/ They point to different resources. Of course most people treat these two URLs as the same, but they don't have to be.

majewsky 9y ago
Do they? They're both retrieved by issuing the same HTTP request: GET / HTTP/1.1 Host: www.tesla.com You cannot leave the path after the method empty in HTTP.
- chrismcb 9y ago
  They are both retrieved because the server handles it. Of course you can leave the path empty. From the RFC: > path = path-abempty ; begins with "/" or is empty A better way to look at it is how w3.org defines it: > h t t p : / / hostport [ / path ] [ ? search ] > path : Void | segment [ / path ] Notice how the slash is in the optional part.
  - JoshMnem 9y ago
    I've never seen a site that doesn't serve a root path. You can't serve a homepage at http://example.comindex.html http://example.comindex.html. I'd be curious to see if it's possible to serve one at http://example.com?page=home http://example.com?page=home, http://example.com#home http://example.com#home, or something like that though. In any case, http://www.tesla.com http://www.tesla.com is not the URL of their home page -- it's http://www.tesla.com/ http://www.tesla.com/ even though the browser tries to tell you that you're visiting http://www.tesla.com http://www.tesla.com.