-
Notifications
You must be signed in to change notification settings - Fork 326
CORS functionality cannot be disabled with property 'graphql.servlet.cors-enabled' #763
Comments
This seems to be a duplicate of #682, which was already resolved (although the fix is not yet in the latest release, only in snapshot version). |
Ah yes, you're right. I'll be looking out for the new release then. |
The issue still exists in the spring-boot 2.7.1 version. |
@kumaritian I've just tested this using the reproduction script of the original reporter with v13.0.0 icw Spring Boot and can confirm it is actually solved. So you must be doing something differently or are experiencing some other kind of issue. |
@oliemansm : In which Spring boot version the issue got resolved. Currently I am using 2.7.1 version. |
@kumaritian It's not a specific Spring Boot version. It's resolved in graphql-spring-boot, so you need to upgrade that to v13.0.0 |
@oliemansm : After upgrading to V13.0.0 from V12.0.0, I am getting below error during application start up but with V12.0.0 there is no issue as application is started successfully.
Note:
Error |
This should be a separate discussion in Q&A instead of hijacking this issue for this problem. It's not related. Remove the |
@oliemansm : Thanks for the input and I did removed |
Open a separate discussion for this to get further assistance. |
@oliemansm : Thanks for your support. FYI : I have created a new issue #856 |
Describe the bug
The GraphQLWebAutoConfiguration class contains a 'corsConfigurer' bean factory method which has a @ConditionalOnProperty annotation with the value of 'graphql.servlet.corsEnabled'. This does not match with the 'graphql.servlet.cors-enabled' config parameter which is the expected format of such a property and therefore it doesn't prevent the CorsFilter to be created when you define the 'graphql.servlet.cors-enabled' config parameter with the value 'false'.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
The breakpoint should not have been reached and therefore the CorsFilter should not have been created.
Screenshots
N/a
Desktop (please complete the following information):
N/a
Additional context
N/a
The text was updated successfully, but these errors were encountered: