Skip to content

feat: custom headers are not passed to all websocket clients #6520

@JoshVee

Description

@JoshVee

When passing custom headers to the Coder CLI (via --header \ $CODER_HEADER), these are not currently getting passed to all websocket connections. This can result in issues, for example, if a custom header is required for authentication.

Example:

➜  coder git:(master) coder templates push mytesttemplate -d templates/aws-linux 
> Upload "templates/aws-linux"? (yes/no) yes
✔ Queued [45ms]
⧗  Running
unexpected non-JSON response "text/html".
begin streaming logs: unexpected status code 200: unexpected non-JSON response "text/html"
	Error: <!DOCTYPE html>

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy