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.
As I've said on the mailing list, I'm not 100% sure whether this is the correct usage of the fastcgi API, so I would really appreciate if somebody with fastcgi (and FPM) knowledge could give a review.
Furthermore, if somebody could give me some pointers in how to write tests for FPM, I will gladly provide tests for this too.
This fixes bug 70279:
in commit f20118a the call to fcgi_hash_init() moved out of the actual request handling to the point where FPM was only calling it once when it spawns a subprocess.
Because the datastructure was not cleaned between handling multiple requests, headers and other data of previous requests were not cleaned correctly.
This patch now calls fcgi_hash_clean() before handling individual requests at the cost of a bit of the performance gains of the previous commit.