Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Does not allow debugging when response header is content-type json #8

Open
sneakingJ opened this issue Mar 13, 2018 · 10 comments
Open

Comments

@sneakingJ
Copy link

When you set the response header for example to 'Content-type', 'application/json; charset=utf-8', you can't activate the debug helper in browser tab.

@sh3bang
Copy link

sh3bang commented Jul 13, 2018

confirmed, same problem

@BrianGilbert
Copy link
Owner

what was the full URL of page you were visiting, it should appear for any url containing http/https

@sneakingJ
Copy link
Author

It was an internal URL I used for developing. But the issue is the case for every page that outputs in json, like this: https://jsonplaceholder.typicode.com/posts

@xojins
Copy link

xojins commented Sep 7, 2018

I have the same problem debugging an API. As a workaround, I navigated to the site's homepage/documentation page and enabled the debugging icon there. I then navigated to the API endpoint and my IDE started debugging properly.

@dejwid
Copy link

dejwid commented Nov 26, 2018

Same problem, the icon does not change to green when i click on it

@judahnator
Copy link

+1 to this issue, JSON content types will not work with this extension

@b-viguier
Copy link

Seems related to Firefox Json viewer 🤔
Here my workaround:

  • Go to about:config
  • Search for devtools.jsonview.enabled and disable it
  • Install an other Json viewer (Json-lite do the job for me)

@acirulis
Copy link

acirulis commented Mar 1, 2020

Workaround with disabling jsonview worked, however permanent solution would be great as debugging APIs are getting more common.

@muster-mark
Copy link

This issue is still occurring. I notice this has been arround for over 3.5 years, should we assume this is a WONTFIX?

@LeoniePhiline
Copy link

I'd still love to see this fixed :)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

10 participants