-
Notifications
You must be signed in to change notification settings - Fork 398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
KCP: stop messing with the RawPath #1883
KCP: stop messing with the RawPath #1883
Conversation
…coded. The Path always fully expands the URL. Since we trim the Path, naturally we would like also to trim the RawPath. To do that correctly we would have to consider encoded slash char as well (%2F). For example the code breaks on %2Fclusters%2F*/apis/apis.kcp.dev/v1alpha1/apiexports Because we don't really need to deal with encoded chars and we don't use the RawPath only the Path we could simplify. This PR simply recomputes the URL after trimming and overwrites it in the HTTP requests.
/assign @stevekuznetsov @sttts |
newURL, err := url.Parse(req.URL.String()) | ||
if err != nil { | ||
responsewriters.ErrorNegotiated( | ||
apierrors.NewInternalError(fmt.Errorf("unable to resolve %s, err %w", req.URL.Path, err)), |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it is InternalError because it is on us. Not sure if we want to expose all the details to an end user.
return | ||
} | ||
req.URL.RawPath = req.URL.RawPath[slash:] | ||
newURL, err := url.Parse(req.URL.String()) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
since we don't really use the RawPath we could simply overwrite the Path and leave the RawPath untouched.
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: sttts The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Generally, the RawPath is only available when some chars have been encoded. The Path always fully expands the URL.
Since we trim the Path, naturally we would like also to trim the RawPath. To do that correctly we would have to consider encoded slash char as well (%2F).
For example the code breaks on %2Fclusters%2F*/apis/apis.kcp.dev/v1alpha1/apiexports
Because we don't really need to deal with encoded chars and we don't use the RawPath only the Path we could simplify.
This PR simply recomputes the URL after trimming and overwrites it in the HTTP requests.
Summary
Related issue(s)
Fixes #