-   Notifications  
You must be signed in to change notification settings  - Fork 367
 
Merge develop into PR #617: Fix incorrect multipart boundaries for plain HTTP #768
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
   Open  
  saksham-postman wants to merge 6 commits into postmanlabs:develop       Choose a base branch                                                 from saksham-postman:saksham-pr617-update                
 base: develop
Could not load branches
    Branch not found: {{ refName }} 
     Loading  
 Could not load tags
   Nothing to show
        Loading  
 Are you sure you want to change the base?
 Some commits from the old base branch may be removed from the timeline, and old review comments may become outdated. 
    Open  
 Changes from all commits
 Commits 
  Show all changes 
  6 commits   Select commit Hold shift + click to select a range 
 37b042f  Fixed implementation of multipart boundaries, adjusted test cases 
  thinkgruen 375a8f5  Adjusted setting of boundaries in loop 
  thinkgruen 4ababe3  adjusted content-length in fixtures 
  thinkgruen 240192b  Always include closing boundary for consistency with current implemen… 
  thinkgruen 51b756e  Merge develop into PR 617 
  saksham-postman bccd60d  fix sdk request 
  saksham-postman File filter
Filter by extension
Conversations
 Failed to load comments.  
    Loading  
 Jump to
  Jump to file  
  Failed to load files.  
    Loading  
 Diff view
Diff view
There are no files selected for viewing
   This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters   
        This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters   
        This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters   
        This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters. Learn more about bidirectional Unicode characters   
      Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.    
 
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).