Closed JerryWang20 closed 2 days ago
This is the expected behavior ... we by default secure the GraphQL server .... however ... the new bcp should pick up the schema file with rc2 and use this instead of introspection ...
if we want to expose the schema, how to enable it?
i install bcp and try to open the schema with same error return
@michaelstaib any document describe the steps?
@JerryWang20
builder.Services
.AddGraphQLServer()
.RemoveIntrospectionAllowedRule();
Product
Hot Chocolate
Version
14.0.0 rc1
Link to minimal reproduction
https://github.com/ChilliCream/graphql-platform
Steps to reproduce
The function works well in locala VS, after deploy to Azure. open the schema with error "Introspection is not allowed for the current request". But i already setting following in the code. Pls help on how to fix this builder.Services.AddGraphQLServer() .AllowIntrospection(true)
What is expected?
Should open the graphql schema
What is actually happening?
The function works well in locala VS, after deploy to Azure. open the schema with error "Introspection is not allowed for the current request". But i already setting following in the code. Pls help on how to fix this builder.Services.AddGraphQLServer() .AllowIntrospection(true)
Relevant log output
No response
Additional context
No response