4 ms·
That's not a safe assumption, especially in the presence of a CMS system. foo.com/bar and foo.com/bar/ (-> foo.com/bar/index.html) can be totally seperate URLs
by TylerE 14y ago
That's not a safe assumption, especially in the presence of a CMS system.
foo.com/bar and foo.com/bar/ (-> foo.com/bar/index.html) can be totally seperate URLs.
- Goopplesoft 14y agoYou're missing his point. Its a safe assumption in the case that the latter gives you an error pointing you to the former. If the latter was a blank/meaningful response that would make sense, but its not.
- nolok 14y agoYou misunderstood OP, the FB error he describe is not about hitting a url "path/" that 301 to "path" and FB not detecting it. In the uri standards, /path and /path/ are just as different as /path and /path2.