fix: use browser-matching multipart boundary format#435
Merged
Conversation
Move multipart boundary generation from JS to Rust so it can use the configured browser fingerprint. Chrome profiles now produce `----WebKitFormBoundary*` and Firefox produces `---------------------------*` matching real browser behavior. Closes #432
github-actions
Bot
added
the
t-tooling
Firefox uses `----geckoformboundary` + two random uint64 in hex, not `---------------------------` + digits. See mozilla-firefox/firefox@main/dom/html/HTMLFormSubmission.cpp#L355
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
2 participants
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.
Moves multipart boundary generation from JS to Rust where the browser fingerprint is available. Each browser profile now produces boundaries matching the real browser format:
----WebKitFormBoundary+ 16 alphanumeric chars----geckoformboundary+ two random uint64 hex valuesxxxxxxxx-xxxx-4xxx-yxxx-xxxxxxxxxxxx)----formdata-impit-*(default, unchanged)The boundary is generated lazily — the NAPI call only happens when the body is actually a
FormDatainstance. The method is not exposed in public types.Closes #432