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
{{ message }}
This repository has been archived by the owner on Jun 26, 2023. It is now read-only.
I think that could be confusing: when the "Opening ..." dialog shows, the user might expect that the content she wants to display in the browser is what the server responded to the active request.
As of now, the extension requests the content again, but that's an ugly workaround for removing the Content-Disposition header.
And I'm not found of adding an option for this in the UI, it seems to be an infrequent use case. I think it would be more appropriate to use a specific tool for this task (REST debugger, ...).
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
That would provide the ability to "content negotiate" a URL--asking it for
application/json
, etc.Thanks for building this!
The text was updated successfully, but these errors were encountered: