This is related #785, but also distinct.
Behind an HTTP proxy with a custom certificate, it's not possible to use the railway CLI, which I needed to ssh into my services.
There are two issues:
- The system certificate store is not respected, so I get a certificate error when trying to do anything that accesses the Railway API.
- The websockets do not respect the environment proxy confiuguration like the normal HTTP requests do, because websockets do not use
reqwest for the initial HTTP connection.
I have a PR that fixes both issues: #807.
I've had to open several tooling proxy PRs in the past, so this isn't my first one. 😁
The PR gets railway CLI working perfectly on my network. Sorry for opening the PR before the issue, I just needed to actually do the implementation to make sure I understood what was wrong. I'd appreciate any review and feedback.
This is related #785, but also distinct.
Behind an HTTP proxy with a custom certificate, it's not possible to use the railway CLI, which I needed to ssh into my services.
There are two issues:
reqwestfor the initial HTTP connection.I have a PR that fixes both issues: #807.
I've had to open several tooling proxy PRs in the past, so this isn't my first one. 😁
The PR gets railway CLI working perfectly on my network. Sorry for opening the PR before the issue, I just needed to actually do the implementation to make sure I understood what was wrong. I'd appreciate any review and feedback.