Repository navigation
Conversation
TimWolla
approved these changes
Oct 11, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The CLI SAPI (for its built-in web server) and FPM both implement
apache_request_headers()withPHP_FUNCTION(apache_request_headers), so both define the C symbolzif_apache_request_headers. That makes it impossible to link the two SAPIs into the same executable: the link fails with a duplicate symbol.This renames FPM's implementation to
fpm_request_headers(the name suggested in the review of #23558), and mapsapache_request_headers()andgetallheaders()to it with@implementation-alias. There is no behavior change: the PHP functions are unchanged.Why
It is extracted from #24192. The rename can be merged on its own as it cleans up the naming (since the function is related to FPM, not apache).