Idea - Make REST API Log Redaction Case Insensitive

Champion

Make REST API Log Redaction Case Insensitive

New

Backend

When you configure Log Redaction to "Yes" it is only redacted if the header is sent on the exact same case as seen on Service Studio. It should have been case insensitive as RFC 7230 Section 3.2 states:

Each header field consists of a case-insensitive field name followed by a colon (":"), optional leading whitespace, the field value, and optional trailing whitespace.

This behavior happens with or without Name in Request set.

14 Mar 2025

Lokesh Kumar Yadav

I agree with your point. According to RFC 7230 Section 3.2, HTTP headers are case-insensitive, meaning they should be treated the same regardless of case. It's reasonable to expect that Log Redaction in OutSystems would adhere to this standard and be case-insensitive.

Having it case-sensitive, as you've pointed out, could lead to unexpected behavior, especially if headers are sent with variations in case. A case-insensitive approach would align better with the HTTP specification and ensure more consistent and reliable redaction, regardless of the case used in the header.

This is definitely a valuable observation for improving the Log Redaction feature. Would you like assistance in raising this as an enhancement request or preparing further details for submitting this feedback?

07 May 2025