mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #4405] [bug]: post json+base64 content bug #1614
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#1614
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 @aaronpeng2020 on GitHub (Oct 5, 2024).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/4405
Is there an existing issue for this?
Current behavior
When sending json content, if the content contains a base64-encoded image and contains the "
//" character, the content after "//" will not be sent.Steps to reproduce
Sent data:
Received data
The truncated position is:
RfEE1vyDKo//sRa1qy3mxJust after the
//character, when I changed//to/\/, the server can receive the complete content.And I use postman in the same environment and it works fine
Environment
Production
Version
Cloud
@shuaixr commented on GitHub (Oct 5, 2024):
github.com/hoppscotch/hoppscotch@fdb250a608/packages/hoppscotch-common/src/helpers/utils/EffectiveURL.ts (L478-L479)reproduced in v2024.9.0. It seems related to the recently merged #4335
@AndrewBastin commented on GitHub (Oct 5, 2024):
@aaronpeng2020 @shuaixr As @aaronpeng2020 mentioned, the fix is merged into #4335.
We have one more bug we are looking into, once that is fixed, we will push out the patch release. Should happen in like a day.
@aaronpeng2020 commented on GitHub (Oct 5, 2024):
Great job, it was really quick.
@jamesgeorge007 commented on GitHub (Oct 7, 2024):
Hi, we have a patch release out. Please let us know if the issue persists.