chore(emulation): fix process transport binary resolution and safari profiles#20
Merged
Conversation
…profiles process transport: resolve curl_impersonate binary per browser profile (curl_chrome145, curl_firefox147, etc) instead of using generic binary. add impersonateTarget to Browser enum and Profile. add -sS flag for detailed error messages in stderr. safari profiles: convert v18/iPad18/iOS18 from wreq profiles to ci profiles matching curl_safari180 binary wire fingerprint. add ciHttp2_180 with ENABLE_CONNECT_PROTOCOL setting. remove unused wreq helpers (baseTlsOptions, baseHttp2Options, baseHeaders, baseHeaderOrder, buildProfile, CIPHER_LIST, SIGALGS_LIST). fix FfiTransport SOCKS5 proxy type from 7 to 5 (was using SOCKS5_HOSTNAME value).
…inary chrome 131: remove maxConcurrentStreams and maxFrameSize from wreq profile — curl_chrome131 binary does not send these settings. firefox 135: remove maxConcurrentStreams and maxHeaderListSize from wreq profile — curl_firefox135 binary does not send these settings. verified: all 41 available binaries now produce zero profile-vs-wire mismatches against tls.peet.ws.
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.
Summary
ProcessTransport binary resolution
curl_impersonatebinary per browser profile (curl_chrome145,curl_firefox147,curl_safari180, etc.) instead of using the genericcurl-impersonatebinaryimpersonateTarget()toBrowserenum — maps each browser to its curl_impersonate binary suffiximpersonateTargetfield toProfile, set byCatalog::resolve()-sSflag for detailed error messages in stderr (was losing curl error details with just-s)Safari profile alignment
v18/iPad18/iOS18from wreq profiles to CI profiles matchingcurl_safari180binary wire fingerprintciHttp2_180()withENABLE_CONNECT_PROTOCOLsetting (Safari 18.0 sends setting 8:1, Safari 18.4+ does not)baseTlsOptions,baseHttp2Options,baseHeaders,baseHeaderOrder,buildProfile,CIPHER_LIST,SIGALGS_LIST)Fix
FfiTransportSOCKS5 proxy type from7to5(was incorrectly usingSOCKS5_HOSTNAMEvalue)Verified against wire
All browsers tested against
tls.peet.wsproduce unique, correct TLS/HTTP2 fingerprints via ProcessTransport:Test plan
SafariTestupdated: v18 now testsgreaseEnabled=trueandpseudo=msap