mirror of
https://github.com/hoppscotch/hoppscotch.git
synced 2026-04-25 16:55:59 +03:00
[GH-ISSUE #180] POST request json bodies aren't sent #70
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#70
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 @AndrewBastin on GitHub (Oct 3, 2019).
Original GitHub issue: https://github.com/hoppscotch/hoppscotch/issues/180
Describe the bug
The POST request body (from the built-in JSON editor) does not seem to reach the recipient.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Well, the server should display the correct body
@liyasthomas commented on GitHub (Oct 4, 2019):
Can you submit a screenshot of console?
@AndrewBastin commented on GitHub (Oct 4, 2019):
The first 2 are through postwoman (preflight and the actual request respectively)
The third is from Postman which is the intended result
@liyasthomas commented on GitHub (Oct 4, 2019):
chuckle i'm in danger
Did you check the network tab and the request info? Check network tab and see if the requests has body.
POST for other servers seems to be working for both raw and key-value pairs.
@SimplyComplexable commented on GitHub (Oct 4, 2019):
@liyasthomas I can take a look into this.
@AndrewBastin commented on GitHub (Oct 4, 2019):
@SimplyComplexable feel free to do so 😊
@AndrewBastin commented on GitHub (Oct 4, 2019):
Oops, sorry, it was a thing with body-parser and Content-Type definitions 😓
Closing the issue, sorry guys 😅