Skip to content

docs: Clarify that http_proxy is not used for HTTPS requests#475

Merged
t-lo merged 3 commits intoflatcar:mainfrom
aaronk6:main
Mar 4, 2026
Merged

docs: Clarify that http_proxy is not used for HTTPS requests#475
t-lo merged 3 commits intoflatcar:mainfrom
aaronk6:main

Conversation

@aaronk6
Copy link
Contributor

@aaronk6 aaronk6 commented Sep 9, 2025

Update documentation: Clarify that http_proxy is not used for HTTPS requests

While experimenting with proxy settings in a Butane config, I noticed that https_proxy must be explicitly set for HTTPS requests to go through the proxy. Setting only http_proxy will proxy plain HTTP requests, but HTTPS requests still go out directly.

However, the documentation previously stated that http_proxy would also be used for HTTPS requests unless overridden by https_proxy. This is incorrect, as confirmed on Matrix.

This PR updates the documentation to reflect the actual behavior.

@aaronk6 aaronk6 requested a review from a team as a code owner September 9, 2025 19:15
@aaronk6
Copy link
Contributor Author

aaronk6 commented Sep 10, 2025

Thanks. The Flatcar docs copy of the Ignition config spec also needs to be fixed.

Oh, missed that. Just updated my PR.

Also, we should do the same change upstream in the Ignition specs and Butane specs (linked specific files here but there's a copy for each variant/version)

I’ll look into this, too.

Copy link
Member

@pothos pothos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks, looks good, I wonder if we should wait until this is also merged upstream (Butane and Ignition repos) or it might get overwritten once we need to sync a newer version of the specs?

@t-lo t-lo merged commit 195a04c into flatcar:main Mar 4, 2026
1 check failed
@github-project-automation github-project-automation bot moved this from ✅ Testing / in Review to Implemented in Flatcar tactical, release planning, and roadmap Mar 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

3 participants