Skip to content

Boundaries for multipart requests in plain HTTP are incorrect #616

Open
@thinkgruen

Description

@thinkgruen

Describe the bug
Currently, the Code Generator for (plain) HTTP is using the same boundary everywhere instead of following the RFC. When trying to send the generated code through an HTTP client, e.g. in IntelliJ, the IDE will point out that the boundaries are incorrect, and the request will fail.

To Reproduce
Steps to reproduce the behavior:

  • create a POST using a form-data body
  • add a key "foo" and text value "bar"
  • generate the HTTP code

Expected code snippet and corresponding request
The generated code is correct according to the definition of the aforementioned RFC which means:

  • there is a boundary defined alongside Content-Type: multipart/form-data (let's say xyz)
  • the boundary is used to separate different form data with two additional hyphens before (--xyz)
  • the request ends with a boundary with two leading and trailing hyphens (--xyz--)

Screenshots
All boundaries are identical but should follow the rules above.
A screenshot of the generated code

Additional context
Version of postman-code-generators/Postman app: 9.16.1

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions