Release Notes / Version 10.2101
Table Of ContentsCache-Control strategy can use full request paths
The
DefaultCacheControlStrategy
can now be configured to use the full request path for pattern matching. When a request contains a semicolon in the path everything after a semicolon is cut in advance of applying the "for-url-pattern". This can be avoided by setting the "cae.cache-control.urlPath.removeSemicolonContent=false" configuration property. Additionally the "cae.cache-control.urlPath.useAlwaysFullPath" and "cae.cache-control.urlPath.urlDecode" configuration properties can be used to adapt the taken request URI path.
(CMS-19195)
Configure CORS allowed origins with Studio host for preview CAE
The documentation of the
cae.cors.allowed-origins-for-url-pattern
configuration property has been extended with a suggestion to configure it with the Studio host for preview CAE. Furthermore the default Studio host was added to the
cae.cors.allowed-origins-for-url-pattern
configuration property in the
application-dev.properties
of the preview CAE.
Please note that no similar configuration has been added to the default
application.properties
for the preview CAE, because we cannot anticipate allowed origins for production environments.
(CMS-18954)