-
Notifications
You must be signed in to change notification settings - Fork 352
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merge develop into PR #617: Fix incorrect multipart boundaries for plain HTTP #768
base: develop
Are you sure you want to change the base?
Merge develop into PR #617: Fix incorrect multipart boundaries for plain HTTP #768
Conversation
Fixed linting fixed looping
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@saksham-postman Changes looks good but there's a test case that's failing.
@VShingala fixed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a comment.
@@ -1,7 +1,7 @@ | |||
let _ = require('./lodash'), | |||
path = require('path'); | |||
|
|||
const FORM_DATA_BOUNDARY = '----WebKitFormBoundary7MA4YWxkTrZu0gW', | |||
const FORM_DATA_BOUNDARY = '--WebKitFormBoundary7MA4YWxkTrZu0gW', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@saksham-postman It seems we have a reason to keep ----
here. Chrome dev tools uses ----
as starting sequence for boundary.
I think we should keep using ----
instead of just --
for better compatibility.
You can see this issue to see how the boundary can be seen in dev tools for reference. (postmanlabs/postman-app-support#11084).
@VShingala @saksham-postman Are we continuing with this PR for fixing this issue? |
This PR merges the latest changes from the
develop
branch into the work done in PR #617 (Fix incorrect multipart boundaries for plain HTTP).Changes:
develop
branch into the feature branchThis PR is intended to update PR #617 with the latest changes from
develop
, ensuring it's up to date with the current state of the project. Once this PR is merged, it will bring PR #617 up to date withdevelop
.Related PR: #617 (Fix incorrect multipart boundaries for plain HTTP)
@thinkgruen Please review these changes and let us know if any further modifications are needed.