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 https://github.com/apiaryio/api-blueprint/issues/100 gets implemented in API Blueprint, the API Elements asset should contain the body with \r\n, not with \n.
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 https://github.com/apiaryio/api-blueprint/issues/100 gets implemented in API Blueprint, the API Elements asset should contain the body with
\r\n
, not with\n
.Example API Blueprint:
Resulting asset:
Expected resulting asset: