Skip to content

Conversation

@xorgy
Copy link
Contributor

@xorgy xorgy commented Jan 13, 2021

Fixes #561

@xorgy xorgy requested a review from slipset as a code owner January 13, 2021 16:18
@slipset
Copy link
Member

slipset commented Jan 13, 2021

Thanks a lot xorgy. Could you please also provide a test which shows that this doesn't break existing functionality, ie that it works when only sending "Upgrade" in the connection header, as well as when sending "keep-alive,Upgrade"?

@xorgy
Copy link
Contributor Author

xorgy commented Jan 13, 2021

Thanks a lot xorgy. Could you please also provide a test which shows that this doesn't break existing functionality, ie that it works when only sending "Upgrade" in the connection header, as well as when sending "keep-alive,Upgrade"?

Sure, I'll write a test for it. Probably good to have one anyway, given that there are zero tests for this function right now.

@xorgy
Copy link
Contributor Author

xorgy commented Jan 13, 2021

Let me know if the test I've added is satisfactory, I can squash it in.

Copy link
Member

@slipset slipset left a comment

Choose a reason for hiding this comment

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

LGTM

No need to squash, I'll do a squash merge here. Thanks!

@xorgy
Copy link
Contributor Author

xorgy commented Jan 13, 2021

Thank you as well.

@slipset slipset merged commit a704e00 into clj-commons:master Jan 15, 2021
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.

websocket-upgrade-request? doesn't detect connection upgrade when there are other tokens

2 participants