Similar to :#76 but different source.

This is for an Issue a customer raised in Coder directly:coder/coder#17687, after debugging this affects the VS Code extension and using coder cli has different behaviour.

It seems that the Coder Extension misses to pass the --header-command to the CLI while coder cli on it's own will work.

Issue:
I can not start a stopped workspace from a local VSCode instance when Coder is behind a Azure AppProxy (using --header)

Expected behaviour:
Workspace should start

Actual behaviour:
Failed to open workspace

"--global config
...
coder-config-xyz exited with code 1: Encountered an error running "coder start", see "coder start --help" for more information
error: invalid character '<' looking for beginning of value"

Steps to Reproduce
Wait until a workspace is stopped in local VSCode
Reload Window while network was down (has nothing to do with the issue)
When VSCode asks to start the stopped workspace say yes

Coder: 2.20.2
OS: Linux