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
The only way I was able to reproduce this was if I used a token that wasn’t set to a schema yet – either because it was created before there were any schemas, or if it was set to a schema that had been deleted.
I’ve “fixed” this for the next release, but only to make the behavior consistent with Craft 3: you will now get a 400 response with the message Invalid Authorization header, as Craft doesn’t actually consider a token “valid” unless it’s assigned to a schema.
You can work around the error by creating a schema, then re-editing your token and selecting the new schema.
What happened?
Description
Hi! I installed CraftCMS locally with GraphQL enabled. When I tested the graphQL with curl command, it got some errors.
Steps to reproduce
Expected behavior
Return pong
Actual behavior
Get error:
Craft CMS version
4.0.4
PHP version
8.1
Operating system and version
Ubuntu 22.04
Database type and version
MariaDB 10.6.7
Image driver and version
No response
Installed plugins and versions
The text was updated successfully, but these errors were encountered: