➜

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 jaswdr
Recipients jaswdr, op368, orsenthil
Date 2021-05-13.12:37:56
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1620909476.75.0.672168333561.issue40938@roundup.psfhosted.org>
In-reply-to
Content 
@op368 as far as I can see, regarding of any miss interpretation, yes, the RFC has this section:

      "http:g"        =  "http:g"         ; for strict parsers
                      /  "http://a/b/c/g" ; for backward compatibility

What I can understand is that for "http:g" it will be translated to "http:///g" because of backward compatibility, this seems to be an edge case for the parser, since the RFC text also mention that this should be avoided.
History
Date User Action Args
2021-05-13 12:37:56jaswdrsetrecipients: + jaswdr, orsenthil, op368
2021-05-13 12:37:56jaswdrsetmessageid: <1620909476.75.0.672168333561.issue40938@roundup.psfhosted.org>
2021-05-13 12:37:56jaswdrlinkissue40938 messages
2021-05-13 12:37:56jaswdrcreate