feat(sdk)!: server-to-server traffic defaults to in.webdecoy.com - #40
Merged
Conversation
The Node SDK's default apiUrl moves behind Cloudflare fronting (app repo #833): server-to-server connections carry no fingerprint telemetry, so the proxy costs nothing and buys DDoS absorption and rate-limiting in front of ingest. The browser client (@webdecoy/client) deliberately keeps the direct hostname: the visitor ClientHello it produces IS the JA4 signal, and no fronting change may cost a fingerprint. Anyone who set apiUrl explicitly is unaffected. 0.14.0 across the workspaces in lockstep.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Default
apiUrlfor the server-side SDK moves tohttps://in.webdecoy.com(Cloudflare-fronted ingest, app repo #833).@webdecoy/client(browser) stays direct oningest.webdecoy.com— the visitor ClientHello is the JA4 signal.Verified against the live hostname before this PR: 200 via Cloudflare, direct origin connection fails TLS. Explicit
apiUrlconfigs are unaffected. All workspaces bumped to 0.14.0 in lockstep; adapter deps updated.