2 ms·
In what situation would someone be requesting `https://gitlab.com/dashboard.html https://gitlab.com/dashboard.html`? When I go there, I get the exact same page
by jhugo 5y ago
In what situation would someone be requesting `https://gitlab.com/dashboard.html https://gitlab.com/dashboard.html`? When I go there, I get the exact same page as I get at `https://gitlab.com/ https://gitlab.com/`, why was it necessary to support both URLs? Now they're stuck with it of course, if anyone actually uses /dashboard.html, but surely they could just special-case filenames that actually exist, just like they presumably special-case URLs they use like /help already. It doesn't seem necessary to blanket-ban anything with a file extension.
- remram 5y agoOr gitlab.com/dashboard. GitLab, GitHub, etc already have a need to reserve specific usernames (like `org`, `settings`, `projects`, `new`, `explore`, `marketplace`, `help`, ...). Since you already have to blocklist specific names not containing extensions, I really don't see how banning extensions help them. Hopefully we'll know more once their security ticket becomes public.