ComposerSettingsValidator should run `composer config` to determine if HTTPS is enabled

Created on 20 October 2022, about 2 years ago
Updated 31 January 2023, almost 2 years ago

Problem/Motivation

Right now, ComposerSettingsValidator invokes the Composer API to get the secure-http config value. Therefore, it relies on the presence of the Composer API, which is something we're hoping to move away from.

Proposed resolution

Extract the value of the secure-http config value by running composer config secure-http and parsing the output.

📌 Task
Status

Fixed

Version

2.0

Component

Package Manager

Created by

🇺🇸United States phenaproxima Massachusetts

Live updates comments and jobs are added and updated live.
  • Security improvements

    It makes Drupal less vulnerable to abuse or misuse. Note, this is the preferred tag, though the Security tag has a large body of issues tagged to it. Do NOT publicly disclose security vulnerabilities; contact the security team instead. Anyone (whether security team or not) can apply this tag to security improvements that do not directly present a vulnerability e.g. hardening an API to add filtering to reduce a common mistake in contributed modules.

Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

Production build 0.71.5 2024