Transform headers policy should be case insensitive

[exalate-issue-sync]

Describe the bug :

When using transform headers policy the value of the headers should be case-insensitive according to this RFC standard https://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.2.

To Reproduce :

Steps to reproduce the behaviour:

1. Create a simple API
2. Add transform headers policy
3. Whitelist a header for example 'TEST'
4. Now go to debug mode and if you add the header TEST it will keep it
5. Now instead of 'TEST' add 'test' and you will see that it will remove that meaning it is case-sensitive

Expected behaviour :

If I enter TEST or test or any other value that is basically test, it should not remove them.

Current behaviour :

Currently if I whitelist TEST it will only accept TEST with uppercase and if I enter test with lowercase it will regard it as a different header and remove it. So customers must whitelist the same headers with uppercase, lowercase or even different formats.

Desktop :

• Environment: 4.1.2
• Browser: Google Chrome

Attachments

image1.png

image2.png

image3.png

[exalate-issue-sync]

This issue will be fixed in versions 4.0.13, 3.20.24, 4.2.0, 4.1.4