Skip to content

fix(backend): Use proxy url if available for handshake URL #6119

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

Merged
merged 2 commits into from
Jun 13, 2025

Conversation

jacekradko
Copy link
Member

@jacekradko jacekradko commented Jun 13, 2025

Description

When Proxy URL is defined, we must use it to determine the handshake URL.

Checklist

  • pnpm test runs as expected.
  • pnpm build runs as expected.
  • (If applicable) JSDoc comments have been added or updated for any package exports
  • (If applicable) Documentation has been updated

Type of change

  • 🐛 Bug fix
  • 🌟 New feature
  • 🔨 Breaking change
  • 📖 Refactoring / dependency upgrade / documentation
  • other:

Summary by CodeRabbit

  • Bug Fixes

    • Corrected the handshake URL calculation to properly use a configured proxy URL, ensuring accurate redirection in proxy scenarios.
  • Tests

    • Added new test cases to verify correct handshake URL generation when a proxy URL is present, including handling of trailing slashes.

@jacekradko jacekradko requested review from aeliox, wobsoriano and a team as code owners June 13, 2025 19:02
Copy link

changeset-bot bot commented Jun 13, 2025

🦋 Changeset detected

Latest commit: 4d04f87

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 11 packages
Name Type
@clerk/backend Patch
@clerk/agent-toolkit Patch
@clerk/astro Patch
@clerk/express Patch
@clerk/fastify Patch
@clerk/nextjs Patch
@clerk/nuxt Patch
@clerk/react-router Patch
@clerk/remix Patch
@clerk/tanstack-react-start Patch
@clerk/testing Patch

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

Copy link

vercel bot commented Jun 13, 2025

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
clerk-js-sandbox ✅ Ready (Inspect) Visit Preview 💬 Add feedback Jun 13, 2025 7:06pm

Copy link
Contributor

coderabbitai bot commented Jun 13, 2025

📝 Walkthrough

Walkthrough

The update modifies the handshake URL construction logic in the backend service to use a proxy URL from the authentication context when available, instead of always using the default API hostname. Corresponding test cases are added to verify the correct handling of proxy URLs with and without trailing slashes.

Changes

Files/Paths Change Summary
packages/backend/src/tokens/handshake.ts Updated handshake URL construction to use proxyUrl from authentication context if present, with normalization.
packages/backend/src/tokens/tests/handshake.test.ts Added tests to verify handshake URL uses proxy URL (with/without trailing slash) when provided in context.
.changeset/happy-tools-cry.md Added patch note describing the fix for handshake URL calculation when a proxy URL is configured.

Suggested labels

backend


🪧 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.
    • Explain this complex logic.
    • 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 explain this code block.
    • @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 explain its main purpose.
    • @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.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @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.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

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.

Copy link
Member

@brkalow brkalow left a comment

Choose a reason for hiding this comment

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

As a follow up, we should consolidate this logic into authenticateContext, the frontendApi should always respect a proxy setup.

@jacekradko
Copy link
Member Author

@brkalow Agreed

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: 0

🧹 Nitpick comments (2)
packages/backend/src/tokens/handshake.ts (1)

139-143: Trim all trailing slashes for stronger normalisation

replace(/\/$/, '') removes only a single trailing slash.
If someone accidentally configures proxyUrl as https://foo.bar// the double-slash survives and the resulting redirect becomes https://foo.bar//v1/client/handshake, which some servers treat as a different path.

A slightly broader (and still cheap) normalisation is to drop all trailing slashes:

-const baseUrl = this.authenticateContext.proxyUrl
-  ? this.authenticateContext.proxyUrl.replace(/\/$/, '')
-  : `https://${frontendApiNoProtocol}`;
+const baseUrl = this.authenticateContext.proxyUrl
+  ? this.authenticateContext.proxyUrl.replace(/\/+$/, '') // strip *all* trailing slashes
+  : `https://${frontendApiNoProtocol}`;

No functional change for the common case, but it prevents edge-case 404s.

packages/backend/src/tokens/__tests__/handshake.test.ts (1)

180-208: Minor test duplication – consider table-driven test

The two new specs differ only in the input proxyUrl and expectations around the trailing slash. Using it.each (or test.each) keeps the intent clear and trims ~20 lines:

- it('should use proxy URL when available', () => { … });
-
- it('should handle proxy URL with trailing slash', () => { … });
+it.each([
+  ['https://my-proxy.example.com',           'my-proxy.example.com'],
+  ['https://my-proxy.example.com/',          'my-proxy.example.com'],
+])('buildRedirectToHandshake respects proxyUrl %s', (proxyUrl, expectedHost) => {
+  mockAuthenticateContext.proxyUrl = proxyUrl;
+  const headers  = handshakeService.buildRedirectToHandshake('test-reason');
+  const location = headers.get(constants.Headers.Location)!;
+  const url      = new URL(location);
+
+  expect(url.hostname).toBe(expectedHost);
+  expect(url.pathname).toBe('/v1/client/handshake');
+  expect(url.searchParams.get('redirect_url')).toBe('https://example.com/');
+  expect(url.searchParams.get(constants.QueryParameters.SuffixedCookies)).toBe('true');
+  expect(url.searchParams.get(constants.QueryParameters.HandshakeReason)).toBe('test-reason');
+});

Purely a readability / maintenance nicety – feel free to keep as-is if you prefer explicit tests.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 69f8cff and 77a1888.

📒 Files selected for processing (2)
  • packages/backend/src/tokens/__tests__/handshake.test.ts (1 hunks)
  • packages/backend/src/tokens/handshake.ts (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (5)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: Formatting | Dedupe | Changeset
  • GitHub Check: Build Packages
  • GitHub Check: semgrep/ci
  • GitHub Check: Analyze (javascript-typescript)

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: 0

🧹 Nitpick comments (1)
.changeset/happy-tools-cry.md (1)

5-5: Consider tightening the summary phrasing.

The summary is clear, but you might rephrase to an imperative form and generalize slightly, e.g.:
“Fix handshake URL calculation when a proxy URL is configured.”

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 77a1888 and 4d04f87.

📒 Files selected for processing (1)
  • .changeset/happy-tools-cry.md (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: semgrep-cloud-platform/scan
  • GitHub Check: Build Packages
  • GitHub Check: semgrep/ci
  • GitHub Check: Analyze (javascript-typescript)
🔇 Additional comments (1)
.changeset/happy-tools-cry.md (1)

1-3: Changeset header is accurate.

The patch is correctly targeted at @clerk/backend and follows the standard changeset format.

Copy link

pkg-pr-new bot commented Jun 13, 2025

Open in StackBlitz

@clerk/agent-toolkit

npm i https://pkg.pr.new/@clerk/agent-toolkit@6119

@clerk/astro

npm i https://pkg.pr.new/@clerk/astro@6119

@clerk/backend

npm i https://pkg.pr.new/@clerk/backend@6119

@clerk/chrome-extension

npm i https://pkg.pr.new/@clerk/chrome-extension@6119

@clerk/clerk-js

npm i https://pkg.pr.new/@clerk/clerk-js@6119

@clerk/dev-cli

npm i https://pkg.pr.new/@clerk/dev-cli@6119

@clerk/elements

npm i https://pkg.pr.new/@clerk/elements@6119

@clerk/clerk-expo

npm i https://pkg.pr.new/@clerk/clerk-expo@6119

@clerk/expo-passkeys

npm i https://pkg.pr.new/@clerk/expo-passkeys@6119

@clerk/express

npm i https://pkg.pr.new/@clerk/express@6119

@clerk/fastify

npm i https://pkg.pr.new/@clerk/fastify@6119

@clerk/localizations

npm i https://pkg.pr.new/@clerk/localizations@6119

@clerk/nextjs

npm i https://pkg.pr.new/@clerk/nextjs@6119

@clerk/nuxt

npm i https://pkg.pr.new/@clerk/nuxt@6119

@clerk/clerk-react

npm i https://pkg.pr.new/@clerk/clerk-react@6119

@clerk/react-router

npm i https://pkg.pr.new/@clerk/react-router@6119

@clerk/remix

npm i https://pkg.pr.new/@clerk/remix@6119

@clerk/shared

npm i https://pkg.pr.new/@clerk/shared@6119

@clerk/tanstack-react-start

npm i https://pkg.pr.new/@clerk/tanstack-react-start@6119

@clerk/testing

npm i https://pkg.pr.new/@clerk/testing@6119

@clerk/themes

npm i https://pkg.pr.new/@clerk/themes@6119

@clerk/types

npm i https://pkg.pr.new/@clerk/types@6119

@clerk/upgrade

npm i https://pkg.pr.new/@clerk/upgrade@6119

@clerk/vue

npm i https://pkg.pr.new/@clerk/vue@6119

commit: 4d04f87

Copy link
Member

@panteliselef panteliselef left a comment

Choose a reason for hiding this comment

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

🚢

@jacekradko jacekradko merged commit 4319257 into main Jun 13, 2025
39 checks passed
@jacekradko jacekradko deleted the fix/use-proxy-url-for-handshake branch June 13, 2025 19:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants