(Salesforce Apex 2024 Release) InvalidHeaderException in Apex REST API

 



The reason you are encountering the error InvalidHeaderException is due to a recently implemented restriction that states that REST response headers defined in Apex via the RestResponse must match API versions. RFC 7230 is used to validate the header names in the addHeader(name, value) method.

Following the upgrade, many more restrictions have been implemented; you can verify them by visiting the RFC 7230 validation page. Invalid characters, including /(slash), are no longer accepted.

Below is a summary of the information found on the validation page of RFC 7230:

  1. Header Field Syntax: Each header field consists of a case-insensitive field name followed by a colon (":"), optional leading whitespace, the field value, and optional trailing whitespace.
  2. Field Extensibility: Header fields are fully extensible, allowing the introduction of new field names, each defining new semantics. Unrecognized header fields should be forwarded, except when explicitly blocked by the Connection header field.
  3. Field Order: The order of header fields with differing names is not significant. It's recommended to send header fields with control data first for early message processing. Multiple header fields with the same name are allowed, but their order matters when interpreting the combined field value.
  4. Whitespace: Whitespace rules include OWS (optional whitespace), RWS (required whitespace), and BWS ("bad" whitespace). Implementations should adhere to proper whitespace rules.
  5. Field Parsing: Field values are not parsed until a later stage of message interpretation, and no whitespace is allowed between the field-name and colon. Obs-fold (line folding) should be handled correctly.
  6. Field Limits: There is no predefined limit on the length of each header field or the header section as a whole. However, servers should reject overly large header fields, and clients may discard or truncate excessively large header fields.
  7. Field Value Components: Header field values are often defined using common syntax components, such as tokens, quoted-strings, and comments. The backslash ("") can be used for quoting within these constructs.

These restrictions and guidelines ensure proper handling of header fields in HTTP, including RESTful resources, and help maintain the integrity and consistency of HTTP messages.

Comments

Post a Comment

Popular posts from this blog

Understanding the Salesforce Approval Process: A Step-by-Step Guide

Image
The Approval Process in Salesforce is an automated sequence of steps where a record is reviewed and approved (or rejected) by designated users based on predefined conditions. This ensures compliance, proper authorization, and consistency in business operations. Key Objects of an Approval Process 1. ProcessNode (Approval Step Definition) (04b) Defines the approval steps in a process. SELECT Id, Name, DeveloperName, ProcessDefinitionId, Description FROM ProcessNode 2. ProcessInstance (Approval Request) (04g) Created when a record is submitted for approval. Stores the current status and progress of the approval process for that record. Acts like a snapshot, tracking where the approval stands at any given moment. SELECT Id, ProcessDefinitionId, TargetObjectId, Status, CompletedDate, LastActorId FROM ProcessInstance 3. ProcessInstanceHistory  Keeps a record of all actions (audit trails) taken on a specific approval process instance. Logs approvals, rejections, reassignments, and recall...
Read more

How to Give Permissions to Automated Process Users or System Context Users

Image
What is Automated Process Users Automated Process Users are special users created automatically by Salesforce, are essential to the execution of automated jobs and background processes. These users are essential for executing tasks that require no direct human intervention, such as: Flows: Automated Process Users can run Flow automations that perform actions like updating records, sending emails, or creating tasks. Approval Processes: They can act on behalf of users in approval processes, ensuring that approvals move forward even without direct user interaction. Scheduled Jobs: These users can run scheduled jobs that perform maintenance tasks or batch data processing. 1. How to fetch automated process user using SOQL? SELECT ProfileId, name FROM User WHERE Alias = 'autoproc' 2. How to give permission of apex class to automated process user step 1: visit following link <ORG_BASE_URL>/_ui/system/user/ProfileApexClassPermissionEdit/e?profile_id=<Automated_Process_User...
Read more

Salesforce Custom Settings: Optimizing Your CRM for Maximum Efficiency

Image
What is Custom settings Salesforce Custom Settings is similar to custom objects, that allow you to create custom data sets and associate them with your Salesforce organisation. It store data in the application cache, enabling efficient access for various Salesforce functionalities like formula fields, validation rules, Apex, and SOAP API. Why we use Custom settings It allow to store configuration data including default settings for org, application parameters, or any other custom data that can be used in apex or LWC.   Unlike custom objects, they can be accessed without needing to perform SOQL queries, making them faster and more efficient for accessing configuration data. Types of Custom Settings 1.  List Custom Settings It provides a reusable set of static data that can be accessed across your organization, It  doesn’t vary with profile or user.  Examples of list data include three-letter country code abbreviations. 2. Hierarchy Custom Settings It uses a built...
Read more