Reject ineffective fingerprint-forwarding carrier configurations
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 48/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- rust
- Domain
- networking
Research direction
Trace static route construction and routes supplied through resolveConnection, starting from the existing stderr warning for ineffective fingerprint forwarding. Review the route-related tests and add coverage for valid and invalid static and resolved-route combinations; done means construction or resolution rejects incompatible carriers with a route-specific recommendation.
Written by the indexing model from the issue text.
Description
Follow-up from the review of #23.
Problem
A route can request forwardFingerprint: ja3 or ja4 without selecting a carrier that can actually deliver it.
The HTTP-header carrier requires terminated plaintext HTTP/1. Passthrough and HTTP/2 require sourceAddressHeader: proxyProtocolV2. Static routes currently emit only an stderr warning for ineffective combinations, allowing an apparently healthy deployment that silently drops the requested fingerprint. Routes supplied through resolveConnection do not receive equivalent warning or validation.
This leaves downstream controls believing they receive an authoritative fingerprint when no signal is delivered.
Acceptance criteria
- Reject configurations where fingerprint forwarding has no viable carrier, rather than relying on stderr.
- Apply identical validation to static routes and routes supplied through
resolveConnection. - HTTP-header forwarding must require TLS termination and an HTTP/1 upstream path.
- Passthrough and HTTP/2 forwarding must require PROXY protocol v2.
- Validate incompatible UDS/Harper combinations where the immediate consumer does not support the selected PROXY protocol version.
- Return a construction/resolution error that identifies the route and recommends the compatible carrier.
- Add tests for valid and invalid static and resolved-route combinations.
- Dominant language
- TypeScript
- Stars
- 1
- Forks
- 0
- Avg merge
- 11h 49m
- Merged PRs (30d)
- 12
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing guide
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.
More from HarperFast/symphony
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
HarperFast/symphony#91 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
HarperFast/symphony#89 ·
Maintainers usually reply within 1 day
-
Mixed-case SNI forwarded to an older peer during a rolling upgrade can reach its wildcard routeOpen
Difficulty 4/5 3-5 days Newbie friendliness 49/100
HarperFast/symphony#93 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 42/100
HarperFast/symphony#92 ·
Maintainers usually reply within 1 day
-
Difficulty 3/5 1-2 days Newbie friendliness 72/100
HarperFast/symphony#90 ·
Maintainers usually reply within 1 day
All issues in HarperFast/symphony
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
feature request needs triage
Difficulty 1/5 1-3 hours Newbie friendliness 69/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
solidjs/solid-docs#1716 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
thecodacus/pithagoras#380 ·
Maintainers usually reply within 1 day