We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
"@nuxtjs/apollo": "^5.0.0-alpha.3"
Hi, I tried to remove the default "Bearer" authType, reading the documentation here: https://apollo.nuxtjs.org/getting-started/configuration#authtype apollo: { clients: { default: { httpEndpoint: process.env.GRAPHQL_URL, authType: "", } } }
apollo: { clients: { default: { httpEndpoint: process.env.GRAPHQL_URL, authType: "", } } }
But seems not working, in the request headers i always get Authorization: Bearer
I need to remove the default bearer value, keep just the token.
No response
The text was updated successfully, but these errors were encountered:
@alessioraggioli try setting authType to null
authType
null
Sorry, something went wrong.
Tried
apollo: { clients: { default: { httpEndpoint: process.env.GRAPHQL_URL, authType: null, } } }
It set me the default "Bearer" in network auth..
94de367
@Diizzayy how can i get the fix? just reinstalling yarn package?
how can i get the fix? just reinstalling yarn package?
@alessioraggioli Indeed, update to v5.0.0-alpha.4 for the fix to take effect.
v5.0.0-alpha.4
Diizzayy
No branches or pull requests
Environment
"@nuxtjs/apollo": "^5.0.0-alpha.3"
Describe the bug
Hi, I tried to remove the default "Bearer" authType, reading the documentation here:
https://apollo.nuxtjs.org/getting-started/configuration#authtype
apollo: { clients: { default: { httpEndpoint: process.env.GRAPHQL_URL, authType: "", } } }
But seems not working, in the request headers i always get
Authorization: Bearer
Expected behaviour
I need to remove the default bearer value, keep just the token.
Reproduction
No response
Additional context
No response
Logs
No response
The text was updated successfully, but these errors were encountered: