nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Ability to Update/Replace an Existing Response Header with Another Existing Header (TKT-217542)

support

Current behaviour:
When the user tries to update a response header to an existing one, this is not currently possible. The available workaround is to use the "Rename" option under bulk actions for response headers, where the user can search for an existing response header and update it manually however, that only creates more response headers. However, this does not fully address the customer's need.

Expected behaviour:
The customer would like the ability to update an existing response header by replacing it with another already-existing response header – without having to manually rename each one. This is especially important given that the customer manages a large number of response headers, making manual updates time-consuming and inefficient.