7 replaced http://stackoverflow.com/ with https://stackoverflow.com/
source | link

A meta.SE bug came up which also applies to SOFU.

Any URL path ending in a dot produces a low-level server 404low-level server 404, rather than the usual SO 404usual SO 404, even when the dot is part of a string which is supposed to be ignoredignored.

Shouldn't the URLs be sanitized before they are processed so that special characters are treated as literals?

A meta.SE bug came up which also applies to SOFU.

Any URL path ending in a dot produces a low-level server 404, rather than the usual SO 404, even when the dot is part of a string which is supposed to be ignored.

Shouldn't the URLs be sanitized before they are processed so that special characters are treated as literals?

A meta.SE bug came up which also applies to SOFU.

Any URL path ending in a dot produces a low-level server 404, rather than the usual SO 404, even when the dot is part of a string which is supposed to be ignored.

Shouldn't the URLs be sanitized before they are processed so that special characters are treated as literals?

6 replaced http://meta.stackexchange.com/ with https://meta.stackexchange.com/
source | link

A meta.SE bugmeta.SE bug came up which also applies to SOFU.

Any URL path ending in a dot produces a low-level server 404, rather than the usual SO 404, even when the dot is part of a string which is supposed to be ignored.

Shouldn't the URLs be sanitized before they are processed so that special characters are treated as literals?

A meta.SE bug came up which also applies to SOFU.

Any URL path ending in a dot produces a low-level server 404, rather than the usual SO 404, even when the dot is part of a string which is supposed to be ignored.

Shouldn't the URLs be sanitized before they are processed so that special characters are treated as literals?

A meta.SE bug came up which also applies to SOFU.

Any URL path ending in a dot produces a low-level server 404, rather than the usual SO 404, even when the dot is part of a string which is supposed to be ignored.

Shouldn't the URLs be sanitized before they are processed so that special characters are treated as literals?

    Post Closed as "off-topic" by Ilmari Karonen, Martijn Pieters, Josh Crozier, hims056, Lucifer
5 edited tags
| link
4 Rollback to Revision 2
source | link
3 added 157 characters in body
source | link
2 specifically affects url paths, i.e. not query strings which are last in the URL; couldn't resist a title with a trailing period, even though I know it is stripped when the urls are generated; couple minor improvements since I was here
source | link
1
source | link