mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-26 01:06:00 +03:00
[GH-ISSUE #4301] [bug]: attachment in the body disappears after reloading/reopening the page/method #1564
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#1564
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 @KatyaGolyagina on GitHub (Aug 27, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4301
Is there an existing issue for this?
Current behavior
When I use attachments in the post method, they are not saved, the fields become empty.
I expect the attachment to be saved and can be used in the future
Steps to reproduce
Same on https://hoppscotch.io/
Environment
Production
Version
Self-hosted
@sz-2302 commented on GitHub (Oct 9, 2024):
Hi! I would like to work on this issue. Please let me know if I can take it on:)
@AndrewBastin commented on GitHub (Oct 9, 2024):
Hi there,
For the time being, we are considering this as an intentional behaviour. The Hoppscotch Request file doesn't store binary data for the time being to not mess with the bandwidth and size restrictions within the Hoppscotch infra.
We will keep the issue open for the time being to encourage discourse and will probably tackle this in a later date when the situation for this is better, but for the time being, we are not planning on tackling this.