Prism Proxy is not working as expected for binary content types image/jpeg and application/pdf
Nagasures opened this issue · comments
Response code receiving as 500 when prism proxy is running where as same request is working when sent to actual live end point URL. Issue is occurring when request sent to prism proxy URL
Context
unable to implement prism for my team of 10 members
Current Behavior
Prism proxy forwards the request to base server but we receive response with code 500. Same request sends to actual base/live URL instead of proxy URL sends me 200 code.
Expected Behavior
Prism proxy should work as live server
Steps to Reproduce
paths
/anything
post:
requestBody:
content:
image/jpeg
schema:
type: string
format : binary
application/pdf
schema:
type: string
format : binary
- File is being uploaded as binary ( not form-data)
- uploading content types image/jpeg , application/pdf
Environment
Latest version of prism : 5.5.4
Files being uploaded from windows 10 into Linux docker container
When request message is received at Proxy URL ... as a next step Proxy is forwarding the request to Live URL. However format of the file is being modified by Proxy causing the 500 response code.
https://docs.stoplight.io/docs/prism/1593d1470e4df-concepts#content-negotiation this content type is not currently supported in prism. We are tracking this enhancement / feature here: #2349 and will close yours as duplicate.
Thank you for support