Client cannot connect to proxy even if upstream is down
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 12.4k
- Forks
- 509
- PR merge metrics
- No merged PRs in 30d
Description
I am able to connect my client to the proxy even if the upstream server socket is not accepting connections. This means I cannot test all my use cases (e.g. server is absent) because the proxy will accept the connection on behalf of the upstream. When I go to send data it errors, but I would rather the socket is not accepted if upstream is down.
An alternative would be if the upstream rule is disabled then the proxy does not accept connections for that rule.
Behaving in this manner would change the code in which the server accepts connections. During the acceptance, the server would either:
- attempt a connection to upstream and refuse the client if that server could not be established, or
- verify the rules and if enabled was false it would reject the connection
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
Start by reproducing the proxy connection behavior with an absent upstream and with the upstream rule disabled, then inspect the server's connection-acceptance path described in the issue. Decide which proposed rejection behavior is consistent with the project and verify that the client connection is refused before data is sent when the upstream cannot be established or the rule is disabled.
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
- Mostly clear
- Newbie friendliness
- 35/100