On 12/12/2013 10:11 PM, Jeff Trawick wrote:
There's nothing magic about it, and there is indeed the potential for a
problem with the environment variable limitation. Generally I preferred to
have a lower per-request memory use even if it takes another write to send
all the envars to the application.
But if I am reading the code correctly, increasing that number wont
increase the per-request size at all, unless the environment is huge. If
the total environment only took say 2K, that's all that would be allocated.
All I can see from that limit I mentioned is limiting the size of 1
individual environment entry. Admittedly not something you'd run into every
day but I can see no downside to making that be AP_FCGI_MAX_CONTENT_LEN.
Just my $0.02. I'm a complete Apache neophyte and you're a commiter so I
won't argue :)
