-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Hard-coded LogFormat definitions are hard-coded #678
Comments
I would also like to see this feature added.
|
+1 |
We worked around this by copying the httpd.conf.erb template into our role module, and using that version when implementing the apache class:
In our copy of the template, we added the log directives we need. This works, but it means we need to track the puppetlabs/apache module a little more closely for changes. |
Yeah, I can't imagine this to be very nice. |
I highly welcome feedback on #682, while sliding down the hill to the office |
Looks like a good start. Thanks for tackling this!
This should make this change transparent to current users, as it provides the same log format definitions as exist now. |
I would like to second using those as the defaults. Other than that this patch is just what I need. |
@skpy right now, I'm only appending new LogFormats to the list, I'm not replacing anything. |
Hello! We are doing some house keeping and noticed that this issue has been open for a long time. We're going to close it but please do raise another issue if the issue still persists. 😄 |
This module hard-codes the LogFormat names in httpd.conf. That stinks for sites that rely on the X-Forwarded-For header on servers behind a load balancer.
We can use the CustomLog option on a per-vhost setting; but this means that we'd need to declare that option for every single vhost. That stinks, as it introduces a lot of repetition.
It'd be nice if the list of LogFormat definitions in httpd.conf could be added to, at the least.
The text was updated successfully, but these errors were encountered: