Skip to content
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

fix(server/v2): support for url encoded path parameters #23386

Closed
wants to merge 2 commits into from

Conversation

technicallyty
Copy link
Contributor

@technicallyty technicallyty commented Jan 15, 2025

Description

Closes: n/a

  • fixes a bug that would cause matches to fail if a path parameter was URL encoded (i.e. %51 -> Q).

Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct type prefix in the PR title, you can find examples of the prefixes below:
  • confirmed ! in the type prefix if API or client breaking change
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • included the necessary unit and integration tests
  • added a changelog entry to CHANGELOG.md
  • updated the relevant documentation or specification, including comments for documenting Go code
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

Please see Pull Request Reviewer section in the contributing guide for more information on how to review a pull request.

I have...

  • confirmed the correct type prefix in the PR title
  • confirmed all author checklist items have been addressed
  • reviewed state machine logic, API design and naming, documentation is accurate, tests and test coverage

Summary by CodeRabbit

  • Bug Fixes

    • Improved handling of URL-encoded parameters in URI matching
    • Enhanced robustness of parameter extraction from URIs
  • Tests

    • Added new test case to validate URL-encoded value processing
    • Expanded test coverage for URI matching functionality

The changes ensure more accurate and reliable processing of URL-encoded parameters across the application's routing mechanism.

@technicallyty technicallyty requested review from julienrbrt and a team as code owners January 15, 2025 03:09
Copy link
Contributor

coderabbitai bot commented Jan 15, 2025

📝 Walkthrough

Walkthrough

The pull request introduces improvements to URL path parameter handling in the matchURL function of the uriMatcher type. The changes focus on better processing of URL-encoded values by adding a boolean flag isURLEncoded to determine whether to use the raw or decoded path. The modification enhances the URI matching logic to correctly handle and decode URL-encoded parameters, ensuring more robust parameter extraction from URIs.

Changes

File Change Summary
server/v2/api/grpcgateway/uri.go Enhanced URL path parameter handling with URL decoding logic
server/v2/api/grpcgateway/uri_test.go Added test case for URL-encoded URI matching

Sequence Diagram

sequenceDiagram
    participant URI as Incoming URI
    participant Matcher as URI Matcher
    participant Decoder as URL Decoder

    URI ->> Matcher: Receive URI
    Matcher ->> Matcher: Check for URL encoding
    alt URL is encoded
        Matcher ->> Decoder: Attempt to unescape
        Decoder -->> Matcher: Return decoded value
    else URL is not encoded
        Matcher ->> Matcher: Use original value
    end
    Matcher ->> Matcher: Store parameter
Loading

Possibly related PRs

Suggested labels

C:server/v2, C:server/v2 api, backport/v0.52.x

Suggested reviewers

  • julienrbrt
  • aljo242

Finishing Touches

  • 📝 Generate Docstrings (Beta)

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@technicallyty technicallyty added the backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release label Jan 15, 2025
@github-actions github-actions bot added C:server/v2 Issues related to server/v2 C:server/v2 api labels Jan 15, 2025
Copy link
Contributor

@technicallyty your pull request is missing a changelog!

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (2)
server/v2/api/grpcgateway/uri.go (1)

31-40: LGTM! Consider adding a code example in the comment.

The logic for detecting URL encoded paths is correct. The comment could be enhanced with an example to better illustrate when url.RawPath is non-empty.

- // the url.RawPath is non-empty when URL encoded values are detected in the path params.
- // this requires different handling when getting path parameter values.
+ // url.RawPath is non-empty when URL encoded values are detected in the path params.
+ // Example: for URL "/foo/bar/%2Fbaz", RawPath="/foo/bar/%2Fbaz" and Path="/foo/bar/baz"
+ // This requires different handling when getting path parameter values.
server/v2/api/grpcgateway/uri_test.go (1)

81-86: Add test case for URL decoding failure.

The current test case verifies successful URL decoding, but we should also test the fallback behavior when decoding fails. This ensures the robustness of the error handling logic.

Add this test case:

{
    name:     "match with invalid URL-encoded values",
    uri:      "https://localhost:8080/foo/bar/invalid%",
    mapping:  map[string]string{"/foo/bar/{bytes}": "queryAddrBytes"},
    expected: &uriMatch{QueryInputName: "queryAddrBytes", Params: map[string]string{"bytes": "invalid%"}},
},
📜 Review details

Configuration used: .coderabbit.yml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 69defb4 and 19069b9.

📒 Files selected for processing (2)
  • server/v2/api/grpcgateway/uri.go (2 hunks)
  • server/v2/api/grpcgateway/uri_test.go (1 hunks)
🧰 Additional context used
📓 Path-based instructions (2)
server/v2/api/grpcgateway/uri_test.go (2)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.


Pattern **/*_test.go: "Assess the unit test code assessing sufficient code coverage for the changes associated in the pull request"

server/v2/api/grpcgateway/uri.go (1)

Pattern **/*.go: Review the Golang code for conformity with the Uber Golang style guide, highlighting any deviations.

⏰ Context from checks skipped due to timeout of 90000ms (9)
  • GitHub Check: tests (03)
  • GitHub Check: tests (00)
  • GitHub Check: test-simapp-v2
  • GitHub Check: test-system-v2
  • GitHub Check: test-sim-nondeterminism
  • GitHub Check: test-integration
  • GitHub Check: Analyze
  • GitHub Check: build (amd64)
  • GitHub Check: Summary

Comment on lines +64 to +76
var matchValue string
if isURLEncoded {
// we'll try to unescape the URL encoded values,
// but if that doesn't work, we can just try the raw value.
if decodedMatch, err := url.QueryUnescape(matches[i+1]); err == nil {
matchValue = matches[i+1]
} else {
matchValue = decodedMatch
}
} else {
matchValue = matches[i+1]
}
params[name] = matchValue
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue

Fix inverted logic in URL unescaping condition.

There's a critical logic error in the URL unescaping condition. When url.QueryUnescape succeeds, the code uses the encoded value (matches[i+1]) instead of the decoded value (decodedMatch), and vice versa.

Apply this fix:

 if isURLEncoded {
   // we'll try to unescape the URL encoded values,
   // but if that doesn't work, we can just try the raw value.
   if decodedMatch, err := url.QueryUnescape(matches[i+1]); err == nil {
-    matchValue = matches[i+1]
-  } else {
     matchValue = decodedMatch
+  } else {
+    matchValue = matches[i+1]
   }
 } else {
   matchValue = matches[i+1]
 }
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
var matchValue string
if isURLEncoded {
// we'll try to unescape the URL encoded values,
// but if that doesn't work, we can just try the raw value.
if decodedMatch, err := url.QueryUnescape(matches[i+1]); err == nil {
matchValue = matches[i+1]
} else {
matchValue = decodedMatch
}
} else {
matchValue = matches[i+1]
}
params[name] = matchValue
var matchValue string
if isURLEncoded {
// we'll try to unescape the URL encoded values,
// but if that doesn't work, we can just try the raw value.
if decodedMatch, err := url.QueryUnescape(matches[i+1]); err == nil {
matchValue = decodedMatch
} else {
matchValue = matches[i+1]
}
} else {
matchValue = matches[i+1]
}
params[name] = matchValue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backport/v0.52.x PR scheduled for inclusion in the v0.52's next stable release C:server/v2 api C:server/v2 Issues related to server/v2
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants