You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
(this is swagger spec 2.0, swagger ui 3.0.17, I will upgrade in a bit and report back if anything changes)
I have an endpoint that delivers a very large JSON payload (about 46mb, sometimes more).
Obviously that can't be rendered on the browser, but swagger still attempts to and that crashes the browser tab.
Is there a way of forcing swagger to not render/format a response ?
I noticed that if I respond with a Content-Disposition: attachment and Content-Type: application/octet-stream swagger loads the whole response in a javascript Blob and renders a "Download file" link pointing to that blob's url, however I wouldn't want to change my API to satisfy swagger ui. Also, is this documented anywhere ? I could only find people on stack overflow mentioning it.
The text was updated successfully, but these errors were encountered:
Locking due to inactivity.
This is done to avoid resurrecting old issues and bumping long threads with new, possibly unrelated content.
If you think you're experiencing something similar to what you've found here: please open a new issue, follow the template, and reference this issue in your report.
Thanks!
(this is swagger spec 2.0, swagger ui 3.0.17, I will upgrade in a bit and report back if anything changes)
I have an endpoint that delivers a very large JSON payload (about 46mb, sometimes more).
Obviously that can't be rendered on the browser, but swagger still attempts to and that crashes the browser tab.
Is there a way of forcing swagger to not render/format a response ?
I noticed that if I respond with a
Content-Disposition: attachment
andContent-Type: application/octet-stream
swagger loads the whole response in a javascript Blob and renders a "Download file" link pointing to that blob's url, however I wouldn't want to change my API to satisfy swagger ui. Also, is this documented anywhere ? I could only find people on stack overflow mentioning it.The text was updated successfully, but these errors were encountered: