Skip to content

fix: do not use relative URLs for ws connections #5715

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 4 commits into from
Aug 20, 2024

Conversation

vikrantgupta25
Copy link
Member

@vikrantgupta25 vikrantgupta25 commented Aug 18, 2024

Summary

the websockets api recently started respecting the domain and support for relative URLs so we can't rely on every user being on the updated version hence added the extra handling for the same

Related Issues / PR's

Screenshots

NA

Affected Areas and Manually Tested Areas

Copy link

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

@github-actions github-actions bot added the bug Something isn't working label Aug 18, 2024
Copy link

Build Error! No Linked Issue found. Please link an issue or mention it in the body using #<issue_id>

YounixM
YounixM previously approved these changes Aug 19, 2024
@grandwizard28
Copy link
Collaborator

Works on old chrome versions, approving @YounixM

@vikrantgupta25 vikrantgupta25 merged commit f0c9f12 into develop Aug 20, 2024
11 of 12 checks passed
@vikrantgupta25 vikrantgupta25 deleted the use-absolute-url-with-websockets branch August 20, 2024 07:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working DO NOT MERGE
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants