Skip to content
EOL Watch
Search itemsOpen menu

OCIBreaking change

API Gateway: default value for the X-XSS-Protection response header no longer returned

From 11 Feb 2027, the API Gateway service no longer returns a default value for the X-XSS-Protection header on HTTP responses. Oracle states that API Gateway support for the X-XSS-Protection response header is deprecated. Oracle describes the header as non-standard and no longer supported by modern browsers.

Breaking from , 11 Feb 2027

What breaks

From 11 Feb 2027, the API Gateway service no longer returns a default value for the X-XSS-Protection header on HTTP responses. Oracle states that the header is non-standard and is no longer supported by modern browsers, although legacy browsers might still use it. Oracle's instruction about the Content-Security-Policy header applies if you serve web applications through an API gateway. Oracle announced the change on 11 Feb 2026.

What to do

  1. If you serve web applications through an API gateway, make sure that an appropriate Content-Security-Policy header is in place, either served from the backend or generated with a header transformation policy.
  2. If you need to keep the behavior of the X-XSS-Protection header, you can also use a header transformation policy.

For more information about header transformation policies, Oracle refers to its topic Transforming Incoming Requests and Outgoing Responses.

Replacement

Not stated by vendor.

Sources

Last checked against this source on .

Found an error? Report it

The text on this page is drafted with AI assistance from the vendor's text, checked against the official source and approved by a person before it is published. How items are written

Last checked · Added · Changelog for this item