Headless responds to HTTP-Head over REST now as in CM11

In CMCC 11 (2310), Headless Server responded to HEAD requests over the REST-API with 200 and 404 as long as JSLT was enabled (which is the default).

With the introduction of Spring-GraphQL, the HTTP transport layer was redefined by Spring. As a consequence, its basic implementation was only able to respond to POST requests. The ability to respond to GET requests was add by CoreMedia but support for HEAD requests was omitted, as such requests to a GraphQL endpoint are neither covered by the GraphQL-over-HTTP spec, nor does it make sense to respond to a HEAD request on a plain GraphQL endpoint.

Nevertheless, supporting HEAD requests makes sense for the REST-API and in CMCC 11 (2310), Headless Server responded with 200 or 404 to a HEAD request as long as JSLT was enabled. Note that the response was always 200, when JSLT was disabled.

This changed behavior was now reestablished for CMCC 12.

Also note that HEAD requests to the REST-API are not recommended and you should strive for solutions avoiding HEAD requests!

Upgrade Information

(CMS-28337)

Richtext headings are resolved with inline handlers

Before, links to content in richtext headlines were not resolved via GraphQL in fields text, textReferencedContent and textAsTree. The content links are resolved correctly now together with other inline elements, by adding the inline handlers to the headline context.

(CMS-28203)