HTTP Custom Header should support Drupal token replacements

Created on 27 February 2025, about 1 month ago

Problem/Motivation

As a follow up to Authentication Custom Header should support Drupal token replacements Active , I would like to suggest to also make this change for HTTP protocol (Additional HTTP headers)

Proposed resolution

Wrap the use of the value in Token::replacePlain() so that any Drupal tokens set in there can be expanded.

Remaining tasks

  1. Wrap the use of the configuration value
  2. Test

User interface changes

None.

API changes

None.

Data model changes

None.

Feature request
Status

Active

Version

3.0

Component

Code

Created by

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

Production build 0.71.5 2024