Bug reportNov 20, 2026· 0:22· 11 views
Hoppscotch: cURL import silently fails on Charles Proxy exports (escaped quotes + --data-binary before URL)
0:22 total
Comments · 0
Be the first to comment.
Bug reportby SceneRecap AI
highcURL import parser: tokenizing of backslash-escaped double quotes inside double-quoted header values, and URL detection when --data-binary precedes the URL
os: macOSapp: Hoppscotch web (REST client)dpr: 1locale: en-USbrowser: Chromium 151.0.7922.34timezone: Europe/Berlinviewport: 1280x720
Repro steps
- 1.Open Hoppscotch. The default Untitled tab shows GET https://echo.hoppscotch.io.
- 2.Open the command palette.
- 3.Type 'curl' and click the 'Import cURL' option.
- 4.Click the cURL editor in the Import cURL dialog.
- 5.Paste a Charles Proxy style command. It has escaped-quote headers (sec-ch-ua with \"Android WebView\";v=\"134\"), content-type: application/json and --data-binary before the final URL "https://httpbin.org/post".
- 6.Click the Import button.
Expected
The request imports as POST https://httpbin.org/post. The Host, sec-ch-ua-platform, sec-ch-ua and content-type headers are set, and the body holds the JSON with deeplink_url and app_launch_count.
Actual
The request imports as POST with URL https://webview;v=134/. That URL comes from a fragment of the escaped sec-ch-ua header value. The Headers tab shows a count of 3. No error or warning appears in the UI.
Evidence
visualThe pasted command in the editor ends with the URL "https://httpbin.org/post". It contains escaped quotes in the sec-ch-ua header and --data-binary before the URL.
visualAfter import, the URL field reads https://webview;v=134/ instead of https://httpbin.org/post. The method is POST.
visualThe Body tab shows an indicator dot and the Headers tab shows a count of 3. No error toast or warning appears.
visualThe state is unchanged from 17s to 21s, so the wrong URL persists with no user feedback.
consoleTest warning: 'gate 3: imported Charles Proxy cURL (escaped quotes + --data-binary before URL)'. It notes that headers and body are expected to be missing or broken.
networkPOST /api/6744148/envelope returned 429 with a matching console 'Failed to load resource' error. This happened before the import and is likely unrelated telemetry.
consoleA warning about setupSubscriptions appears at load. This is likely unrelated.
Issue markdown (copy-paste ready)
## Summary
Importing a Charles Proxy style cURL command produces the wrong URL. The parser takes `https://webview;v=134/` from inside the escaped `sec-ch-ua` header value. It ignores the real URL `https://httpbin.org/post`. No error is shown.
## Environment
- Chromium 151.0.7922.34, macOS
- Viewport 1280x720, DPR 1
- Locale en-US, timezone Europe/Berlin
- Hoppscotch web, REST client
## Steps to reproduce
1. Open Hoppscotch (0s).
2. Open the command palette (5s).
3. Type `curl` and click **Import cURL** (7.1s).
4. Click the **cURL editor** (9s).
5. Paste the command below (11s).
6. Click **Import** (12.8s).
```
curl -H "Host: httpbin.org" -H "sec-ch-ua-platform: \"Android\"" -H "sec-ch-ua: \"Chromium\";v=\"134\", \"Not:A-Brand\";v=\"24\", \"Android WebView\";v=\"134\"" -H "content-type: application/json" --data-binary "{\"deeplink_url\":\"/api/status\",\"app_launch_count\":1}" --compressed "https://httpbin.org/post"
```
## Expected
POST `https://httpbin.org/post` with Host, sec-ch-ua-platform, sec-ch-ua and content-type headers. The JSON body holds `deeplink_url` and `app_launch_count`.
## Actual
At 15s the request is POST `https://webview;v=134/`. The Headers tab shows a count of 3 and the Body tab shows an indicator dot. No error or warning appears in the UI. The state is unchanged through 21s.
## Evidence
- 11s: The editor shows the full command ending in `"https://httpbin.org/post"`.
- 15s: The URL field shows `https://webview;v=134/`, a fragment of `\"Android WebView\";v=\"134\"`.
- 17.9s: The console test warning `gate 3: imported Charles Proxy cURL (escaped quotes + --data-binary before URL)` says headers and body are expected to be missing or broken.
- 5.2s: `POST /api/6744148/envelope` returned 429. This is likely unrelated telemetry.
## Suspected area
The cURL import tokenizer appears to mishandle backslash-escaped double quotes inside double-quoted arguments. Token boundaries shift, and a header fragment is picked up as the URL. URL detection when `--data-binary` precedes the URL should also be checked.
## Notes
The import fails silently. The user gets no signal that the parse went wrong.
*Recorded with SceneRecap.*Your recordings could explain themselves too.
Free plan · silent recordings welcome · bug reports included.
Try SceneRecap free →