mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 09:16:03 +03:00
[GH-ISSUE #3969] [bug]: Using a file as request body in combination of a custom Content-Type freezes hoppscotch desktop app #1395
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#1395
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 @wavedeck on GitHub (Apr 10, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/3969
Is there an existing issue for this?
Current behavior
I want to send an image file to an api that wants the mime-type of the file as the Content-Type header and the content of the file as a binary body. The only way i've been able to do this in hoppscotch was selecting "text/plain" as the Content-Type in the "Other" category and then selecting the file on the top right.
Hoppscotch's UI freezes for a while and doesn't respond to anything and recovers itself once it loaded and displays the binary content in the raw body input field. My test for a 300kb png file took about 12-15 seconds until hoppscotch recovers.
Another test using multipart/formdata and using the file select resulted in no freeze, so this only really happens in the case where you need a custom Content-Type and upload a file as a body.
Steps to reproduce
Environment
Production
Version
Local
@liyasthomas commented on GitHub (Mar 4, 2025):
Thanks for your patience and valuable feedback. We’ve fixed this bug in the latest release.
Download the latest builds and provide your valuable feedback.
Closing this ticket as this bug is now fixed in the recent version. Please feel free to reach out if you have any other concerns.