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
Is your feature request related to a problem? Please describe.
Currently (version 1.3.6) I'm getting inline;filename=f.txt set in Content-Disposition header. I think it is redundant. For me, it is a bit problematic, because when I'm trying to save the response in Postman, the header is taken into account and f.txt name is suggested.
Describe the solution you'd like
I would like not to have Content-Disposition header set in the response.
Describe alternatives you've considered
Alternatively, the Content-Disposition header could contain more meaningful name like inline;filename=$URL.json or inline;filename=$URL.yaml depending on the docs URL.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
Currently (version 1.3.6) I'm getting
inline;filename=f.txt
set inContent-Disposition
header. I think it is redundant. For me, it is a bit problematic, because when I'm trying to save the response in Postman, the header is taken into account andf.txt
name is suggested.Describe the solution you'd like
I would like not to have
Content-Disposition
header set in the response.Describe alternatives you've considered
Alternatively, the
Content-Disposition
header could contain more meaningful name likeinline;filename=$URL.json
orinline;filename=$URL.yaml
depending on the docs URL.The text was updated successfully, but these errors were encountered: