RFC 3986 and password #1034
Replies: 1 comment
-
|
https://datatracker.ietf.org/doc/html/rfc3986#section-7.5:
It does sound like the application is responsible for deciding this. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The
RFC 3986standard says "Use of the format "user:password" in the userinfo field is deprecated." But, yarl allowspasswordin the authority field eg.This maybe to allow backward compatibility with
RFC 1808. IfRFC 3986compliance is mandatory then my code has to validate theauthorityentries to ensure it doesn't contain apasswordprior to passing toURL.build. Is this correct?Beta Was this translation helpful? Give feedback.
All reactions