Invalid RestResponse headers

Overview

With Spring '24 regardless of API version, Salesforce will enforce all REST response headers defined in Apex via the RestResponse.addHeader(name, value) method to have valid names in accordance with RFC 7230.

Business Impact

Suboptimal resource allocation, increased costs, and delayed time-to-market for new features and products.

Is your Salesforce solution affected by Invalid RestResponse headers?

Clayton detects anti-patterns and offers automated fix advice to kickstart your Well-Architected journey.

Scan your solution

Resources

RFC-7230: Header Fields
Enforce RFC 7230 Validation for Apex RestResponse Headers (Release Update)

Incidence

How common is this issue?

Data not available

Exposure

How long do organizations remain exposed before fixing the problem?

Data not available

Frameworks

Easy

Intentional

Strategy

Technical Debt

Found a mistake?

If you think something is incorrect, missing or misleading please let us know.

Report an error