Skip to content
This repository has been archived by the owner on Oct 6, 2023. It is now read-only.

Support for custom header on WebSocket #19

Closed
Rukenshia opened this issue Jun 7, 2019 · 2 comments
Closed

Support for custom header on WebSocket #19

Rukenshia opened this issue Jun 7, 2019 · 2 comments
Labels
help wanted Extra attention is needed
Projects

Comments

@Rukenshia
Copy link

Hello,

I wanted to try firecamp but got stuck right at the start. I am developing a service that exposes a HTTP endpoint and after checking headers (Authorization in my case), upgrades the connection to a WebSocket. I couldn't find any way to do this with Firecamp right now.

@Nishchit14
Copy link
Contributor

Nishchit14 commented Jun 17, 2019

@Rukenshia Thank you for sharing your use case, Headers do not exist in WebSocket protocol, instead, you can use Protocols to achieve the same thing.

But in your case, It seems like you're upgrading from https to ws. Can you please share some blog/article or GitHub repo to review this use-case? If it is possible then We'll surely implement this feature.

@Nishchit14 Nishchit14 added the help wanted Extra attention is needed label Jun 17, 2019
@Nishchit14 Nishchit14 added this to To do in Firecamp Sep 17, 2019
@Nishchit14
Copy link
Contributor

Released under v1.4.0

@Nishchit14 Nishchit14 moved this from To do to In progress in Firecamp Jul 8, 2021
@Nishchit14 Nishchit14 moved this from In progress to Done in Firecamp Jul 8, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
help wanted Extra attention is needed
Projects
Firecamp
  
Done
Development

No branches or pull requests

2 participants