Skip to content

JSON API content type makes exploring in the browser impossible #1048

@masterspambot

Description

@masterspambot

I would like to target the problem that was introduced in our Kathatrsis library by @Ramblurr:

https://github.com/katharsis-project/katharsis-core/issues/310

Since JSON API uses a custom content type, and Katharsis correctly sets this, the result 
is you can't just view a Katharsis api response in the browser. 

On firefox at least, it prompts you to download the response body.

Perhaps setting Content-Disposition to inline would work?
Has anyone seen this before? What's the workaround?

Do you think that standard should be extended/updated to face the following problem?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions