Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Allow setting KeepAlive related options per vhost #1447

Merged
merged 1 commit into from
May 7, 2016

Conversation

antaflos
Copy link
Contributor

Introduce the parameters vhost::keepalive, vhost::keepalive_timeout and
vhost::max_keepalive_requests, which are all undef by default, meaning
the server-wide KeepAlive options will be in effect. This way the
KeepAlive settings can be changed on a per-vhost basis.

Includes updated documentation and basic spec tests.

Introduce the parameters vhost::keepalive, vhost::keepalive_timeout and
vhost::max_keepalive_requests, which are all undef by default, meaning
the server-wide KeepAlive options will be in effect. This way the
KeepAlive settings can be changed on a per-vhost basis.

Includes updated documentation and basic spec tests.
@igalic
Copy link
Contributor

igalic commented May 7, 2016

What about keepalive as server setting?

@antaflos
Copy link
Contributor Author

antaflos commented May 7, 2016

@igalic
Copy link
Contributor

igalic commented May 7, 2016

what i meant is, if we should change the defaults here https://github.com/puppetlabs/puppetlabs-apache/blob/master/manifests/params.pp#L141-L143 to Apache httpd's actual defaults.

@antaflos
Copy link
Contributor Author

antaflos commented May 7, 2016

I thought it was decided in #1434 that changing the KeepAlive default value is a backwards-incompatible change, no?

@igalic igalic merged commit ebfe4fb into puppetlabs:master May 7, 2016
@igalic
Copy link
Contributor

igalic commented May 7, 2016

right. thank you for the patch

@mmoll
Copy link
Contributor

mmoll commented May 20, 2016

It would have been nice if true/false would have been used instead of 'On'/'Off'. How likely would such a change get accepted?

@antaflos
Copy link
Contributor Author

@mmoll I have used 'on'/'off' to be in line with the way the server-wide KeepAlive parameters are handled. And I think there are quite a few other boolean parameters that require 'on'/'off' instead of true/false.

But there is the bool2httpd function which, I realise, I should have used.

@mmoll
Copy link
Contributor

mmoll commented May 20, 2016

@antaflos I just stumbled over it, as I wanted to use these new params in theforeman-foreman, where we use booleans and a custom template fragment, it's not a big thing. :)

@igalic
Copy link
Contributor

igalic commented May 20, 2016

i think by now we have a any2bool function in stdlib, so in the future, that could be used everywhere
i didn't quite see the light back then when I wrote that function, in anger ;)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants