Skip to content

fix: parse_curl mangles tokens from shlex.split with backslash-newline continuation #18

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Fly143 merged 1 commit into from
Jul 27, 2026
Merged

fix: parse_curl mangles tokens from shlex.split with backslash-newline continuation #18

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions proxy.py
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1438,6 +1438,13 @@ def parse_curl(curl: str) -> dict:
tokens = shlex.split(curl)
except ValueError:
tokens = curl.replace("\\\n", " ").split()
# When cURL uses \\\n (backslash-newline) continuation (e.g. Chrome
# DevTools "Copy as cURL" on macOS), shlex.split preserves '\n' as
# the first character of the following token, producing "\n-H" or
# "\n--data-raw". Strip only leading '\n' — not all whitespace —
# so intentional whitespace in values is preserved.
tokens = [t.lstrip('\n') for t in tokens]
tokens = [t for t in tokens if t]
out = {"url": "", "headers": {}, "body": ""}
i = 0
while i < len(tokens):
Expand Down