-
Notifications
You must be signed in to change notification settings - Fork 23
pass headers to coder api #81
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
Conversation
@Liorba I fixed the header problem in the attached PR: coder/coder#7181 I'll review the rest shortly! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should probably just be a map of header name to string or file path so people can set multiple headers
Co-authored-by: Dean Sheather <[email protected]>
Co-authored-by: Dean Sheather <[email protected]>
@deansheather,I thought about this approach at first, but this is no regular header. it sort of like the session token which is a header but has a special treatments. |
@Liorba is it alright if I work off of your code and change some things? I want to make it more generic so that it's not so VPN-specific (even though that will be the first-class use-case). |
@kylecarbs sure mate!
|
@rodrimaia let's make this more generic with |
We did this in #119! |
Hey coder team this pr tries to tackle issue #76
This pr added the following functionality to the vscode extension:
settings.json
or in fileAxios
global headers.proxyCommand
There is an issue with the coder
vpnssh
command that unlike thessh
command do not pass the headers correctly to the underline ssh command. when I replace it with the "regular" ssh command it worked. any Idea what might causing this?