close

Filter

loading table of contents...

CoreMedia Content Cloud v12 Upgrade Guide / Version 2404

Table Of Contents

7.10.2 Configuration Properties Changes

Note

Probably Necessary to Check and Change

Due to the newly used Spring-GraphQL library, some configuration properties have been renamed and have sometimes new default values. Check all the properties.

Schema Introspection

The Spring-GraphQL library comes with its own implementation of schema introspection and with it also its own configuration property. Thus, the configuration property was removed in favor for Spring-GraphQLs configuration property.

Removed:

caas.graphql.introspectionEnabled

Replaced by:

spring.graphql.schema.introspection.enabled

Type:

Boolean

Default:

false

REST Mapping Controller

The REST mapping for persisted queries was previously handled by a controller, which was removed and replaced by a Spring-GraphQL-Handler and an autoconfiguration class.

Removed:

caas.graphql-restmapping-controller.enabled

To disable the REST mapping feature, add the autoconfiguration class to the SpringBoot exclude list, for example, in an environment variable.

SPRING_AUTOCONFIGURE_EXCLUDE=com.coremedia.caas.web.rest.RestMappingAutoConfiguration
GraphQL Endpoint

The configuration of the GraphQL endpoint is now handled by the Spring-GraphQL library. If you have not changed the standard value /graphql, no further action is necessary.

Removed:

graphql.url

Replaced by:

spring.graphql.path

Type:

String

Default:

/graphql

GraphiQL Endpoint

The web interface GraphiQL (pronounced ‘graphicle’) to the /graphql endpoint is now part of Spring-GraphQL, thus configuration is also handled by Spring-GraphQL.

Removed:

graphiql.enabled

Replaced by:

spring.graphql.graphiql.enabled

Type:

Boolean

Default:

false

Deployment behind Reverse-Proxy Server

When Headless Server is deployed behind a reverse proxy service and the outside protocol is HTTPS, Spring should be configured to forward certain HTTP headers. Otherwise, the protocol, for example, on the Swagger page will cause "Mixed Content" JavaScript issues, because the page tries to issue non-secure request while the page itself is SSL.

To configure this behavior, either use an environment variable or a configuration property.

Environment variable

SERVER_FORWARD_HEADERS_STRATEGY: "framework"

Configuration property

server.forward-headers-strategy=framework

Search Results

Table Of Contents
warning

Your Internet Explorer is no longer supported.

Please use Mozilla Firefox, Google Chrome, or Microsoft Edge.