This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author martin.panter
Recipients hfuru, jerith, martin.panter, orsenthil, vstinner
Date 2017-11-26.03:59:46
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1511668788.14.0.213398074469.issue10231@psf.upfronthosting.co.za>
In-reply-to
Content
The first two bugs ("foo/dir?baz" and "foo/dir?baz/") were solved by Issue 23112. The third (".../foo.html/") was solved by Issue 17324.

That leaves the fourth complaint, which I don’t understand: ‘translate_path() does not handle initial "."/".." on non-Posix systems’.

As far as I know, in 2010 (and still in 2017) the only non-Posix system Python supported was Windows. But Windows has os.curdir = "." and os.pardir = "..", just like Posix.

There is a quirk where requests like “GET .” and “GET ../path” will retain the dots after passing through “posixpath.normpath”. If there was a platform where a single or double dot was a legal file or directory name, the server will access the corresponding file or directory in these cases. But this does not seem like a problem.

I propose to close this, unless there really is a bug with non-Posix systems.
History
Date User Action Args
2017-11-26 03:59:48martin.pantersetrecipients: + martin.panter, hfuru, orsenthil, vstinner, jerith
2017-11-26 03:59:48martin.pantersetmessageid: <1511668788.14.0.213398074469.issue10231@psf.upfronthosting.co.za>
2017-11-26 03:59:48martin.panterlinkissue10231 messages
2017-11-26 03:59:46martin.pantercreate