-
Notifications
You must be signed in to change notification settings - Fork 38.8k
Consistent parsing of user information in UriComponentsBuilder #32211
Copy link
Copy link
Closed
Labels
in: webIssues in web modules (web, webmvc, webflux, websocket)Issues in web modules (web, webmvc, webflux, websocket)status: backportedAn issue that has been backported to maintenance branchesAn issue that has been backported to maintenance branchestype: bugA general bugA general bug
Milestone
Metadata
Metadata
Assignees
Labels
in: webIssues in web modules (web, webmvc, webflux, websocket)Issues in web modules (web, webmvc, webflux, websocket)status: backportedAn issue that has been backported to maintenance branchesAn issue that has been backported to maintenance branchestype: bugA general bugA general bug
Type
Fields
Give feedbackNo fields configured for issues without a type.
The
USERINFO_PATTERNinUriComponentsBuilderwas updated a while ago to ignore other hierarchical components such as path, query, and fragment, but it should do so only for those in order to be consistent with the syntax from RFC 3986, section 3.2 and also withHierarchicalUriComponents.Type.USER_INFO, which follows that syntax.