Client sent an HTTP request to an HTTPS server.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 12.4k
- Forks
- 510
- PR merge metrics
- No merged PRs in 30d
Description
I have kind of a unique situation that can use your help on.
In my environment we terminate TLS at a LB before it gets routed to my toxiproxy instance. Then toxiproxy tries to send to the downstream service over https, but I get the Client sent an HTTP request to an HTTPS server. error.
Basic layout:
Source -> HTTPS LB (TLS Terminated here) -> toxiproxy listening on 8080 -> Downstream HTTPS LB (TLS Terminated here) -> downstream listening on 5050
I can get past it by not pointing it to the downstream HTTPS LB, but I could only hit a single service then, and it would need to be reconfigured anytime a new deployment happens. Not very user friendly.
It seems that toxiproxy only send over TCP, and doesn't try to do https even if its over port 443.
Is there any way I could get around this? Any ideas will be helpful.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue provides no files, tests, or entry points. Start by tracing how toxiproxy handles the TCP path between the TLS-terminated load balancers, then determine whether HTTPS forwarding is expected; done should include a documented or implemented way to reach the downstream HTTPS service without reconfiguring each deployment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- networking
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100