API Platform version(s) affected: v3.1.13
Description
With default configuration, the GraphiQL IDE was always rendered in the browser on route /graphql while that same endpoint supported GraphQL calls. Since yesterday, visiting this in the browser does not render the IDE anymore, but shows the page's source code (the response has content-type: application/json).
The same issue occurs when visiting /graphql/graphiql and /graphql/graphql_playground.
How to reproduce
This happened after rebuilding and restarting the docker compose stack we are using. Rewinding to commits in a time that the issue was not happening kept producing the same issue.
Possible Solution
Workaround, move IDEs to separate routes:
#config/routes.yaml
graphql_playground:
path: /docs/graphql_playground
controller: api_platform.graphql.action.graphql_playground
graphiql:
path: /docs/graphiql
controller: api_platform.graphql.action.graphiql
Additional Context


API Platform version(s) affected: v3.1.13
Description
With default configuration, the GraphiQL IDE was always rendered in the browser on route
/graphqlwhile that same endpoint supported GraphQL calls. Since yesterday, visiting this in the browser does not render the IDE anymore, but shows the page's source code (the response hascontent-type: application/json).The same issue occurs when visiting
/graphql/graphiqland/graphql/graphql_playground.How to reproduce
This happened after rebuilding and restarting the docker compose stack we are using. Rewinding to commits in a time that the issue was not happening kept producing the same issue.
Possible Solution
Workaround, move IDEs to separate routes:
Additional Context