Multipart request bodies need to use \r\n instead of only \n

[honzajavorek]

Multipart request example in API Blueprint results in body asset containing newlines formed by \n only. However, such asset isn't valid and usable as raw HTTP payload, all infrastructure counts with \r\n being in place.

Dredd currently fixes this, but I consider it as a workaround. I think the API Blueprint format should take care of this and to provide user with a correct, raw HTTP representation of a body. I guess if other API description formats support multipart, let's say in some declarative way, or if #100 gets implemented in API Blueprint, the API Elements asset should contain the body with \r\n, not with \n.

• Related: Multipart form requests need to use \r\n instead of only \n  dredd#74, Multipart form requests need to use \r\n instead of only \n #74 dredd#118
• Slightly related: A nicer way to express multipart form submission (with images) #100

---

Example API Blueprint:

FORMAT: 1A

# Testing 'multipart/form-data' Request API

# POST /data

+ Request (multipart/form-data;boundary=---BOUNDARY)

    + Body

            ---BOUNDARY
            Content-Disposition: form-data; name="text"
            Content-Type: text/plain

            test equals to 42
            ---BOUNDARY
            Content-Disposition: form-data; name="json"; filename="filename.json"
            Content-Type: application/json

            {"test": 42}
            ---BOUNDARY--

+ Response 200 (application/json; charset=utf-8)

    + Body

            {"test": "OK"}

Resulting asset:

---BOUNDARY\nContent-Disposition: form-data; name="text"\nContent-Type: text/plain\n\ntest equals to 42\n---BOUNDARY\nContent-Disposition: form-data; name="json"; filename="filename.json"\nContent-Type: application/json\n\n{"test": 42}\n---BOUNDARY--\n

Expected resulting asset:

---BOUNDARY\r\nContent-Disposition: form-data; name="text"\r\nContent-Type: text/plain\r\n\r\ntest equals to 42\r\n---BOUNDARY\r\nContent-Disposition: form-data; name="json"; filename="filename.json"\r\nContent-Type: application/json\r\n\r\n{"test": 42}\r\n---BOUNDARY--\r\n