mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 08:45:58 +03:00
[GH-ISSUE #5910] [bug]: Unable to import cURL with -sS flags #2320
Labels
No labels
CodeDay
a11y
browser limited
bug
bug fix
cli
core
critical
design
desktop
discussion
docker
documentation
duplicate
enterprise
feature
feature
fosshack
future
good first issue
hacktoberfest
help wanted
i18n
invalid
major
minor
need information
need testing
not applicable to hoppscotch
not reproducible
pull-request
question
refactor
resolved
sandbox
self-host
spam
stale
testmu
wip
wont fix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hoppscotch#2320
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @chhaviG22 on GitHub (Feb 26, 2026).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/5910
Originally assigned to: @chhaviG22 on GitHub.
Is there an existing issue for this?
Platform
Web App
Browser
Chrome
Operating System
macOS
Bug Description
When importing cURL commands that contain output control flags (such as
-s,-S,-v,-sS, etc.), the import fails with "cURL is not formatted properly" error. These flags control cURL's output behavior but don't affect the actual HTTP request.Expected Behavior
The cURL command should be successfully imported.
The
-sSflags should be automatically stripped during parsing since they only control cURL's output behavior.Actual Behavior
Import fails with error: "cURL is not formatted properly"
Steps to reproduce
Current Workaround
Manually remove the
-sSflags before importing.Additional context
Interceptor used: N/A (issue occurs during import, before any request is sent)
Deployment Type
Hoppscotch Cloud
Version
2026.2.0
@VishwaVikas2006 commented on GitHub (Mar 12, 2026):
Hi, I'd like to work on this issue. I’ll try reproducing the problem locally and submit a fix if I can identify the cause.