Fix issue with multipart type #9
Merged
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.
Hi,
My backend couldn't process requests when I tried send them from RapiDoc. Backend is based on Python CGI.
I investigated this issue and found a problem here. Request payload contains browser-generated boundary fields, but boundary isn't mentioned in Content-Type header. It confusing my backend.
According to RFC 2616 (section 3.7.2)
Then I read some advices. I think that best solution in this case: is not to specify Content-Type at all (only for multipart data, of course).
It works for me. But I checked it only from Chrome.