puppetlabs-apache icon indicating copy to clipboard operation
puppetlabs-apache copied to clipboard

Published 20 hours ago • verified publisher icon puppetlabs

mod_remoteip doesn't add RemoteIpHeader in vhost

Open mwinkens opened this issue 2 years ago • 7 comments

Describe the Bug

When using apache::mod::remote_ip the vhost doesn't get edited and the keywords aren't added. Therefore the remoteip isn't working, because the X-Forwarded-For header isn't set if apache get's used by a loadbalancer

Expected Behavior

I expect the RemoteIPHeader X-Forwarded-For to be set in the vhost if the module is used

Steps to Reproduce

Steps to reproduce the behavior:

  1. create an apache managed with puppet and served by a loadbalancer which also uses the X-Forwarded-For Header
  2. Use the apache::mod::remote_ip
  3. See, that it's not working because a flag is missing in the vhost

Environment

  • Version [e.g. 1.27.0]
  • Platform [e.g. Ubuntu 18.04]

Additional Context

Add any other context about the problem here.

mwinkens avatar Sep 12 '23 11:09 mwinkens