Skip to content

fix(websocket): client url for development with proxy #3344

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 1 commit into from
May 25, 2025

Conversation

dargmuesli
Copy link
Member

πŸ”— Linked issue

#3343

❓ Type of change

  • πŸ“– Documentation (updates to the documentation or readme)
  • 🐞 Bug fix (a non-breaking change that fixes an issue)
  • πŸ‘Œ Enhancement (improving an existing functionality like performance)
  • ✨ New feature (a non-breaking change that adds functionality)
  • ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

πŸ“š Description

Corrects the websocket client's connection URL so that it also works when a reverse proxy is used in development.

πŸ“ Checklist

  • I have linked an issue or discussion.
  • I have updated the documentation accordingly.

@dargmuesli dargmuesli changed the title fix(websocket): client url fix(websocket): client url for development with proxy May 11, 2025
Copy link

pkg-pr-new bot commented May 11, 2025

npm i https://pkg.pr.new/@nuxt/content@3344

commit: c44756b

@farnabaz farnabaz merged commit d67b63b into nuxt:main May 25, 2025
3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants