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

Unable to set Apache Ports if it includes an IP #563

Open
vollmerk opened this issue May 16, 2017 · 8 comments
Open

Unable to set Apache Ports if it includes an IP #563

vollmerk opened this issue May 16, 2017 · 8 comments

Comments

@vollmerk
Copy link

Currently the ssl_server_port ans server_port only allows integers

  Integer[0, 65535] $server_port = $::foreman::server_port,
  Integer[0, 65535] $server_ssl_port = $::foreman::server_ssl_port,

However Apache allows you to bind to a specific IP+Port, example

Listen 10.50.10.10:80
Listen 10.50.10.11.443

Validation on port/Listen result needs to be significantly more complex :( allowing for IPv4 + Port or IPv6 + Port. I was going to just submit a pull-request but it got messy, so my question is now should there be a crazy IP regular expression which includes the colon and the port range, oooor just string or?

@mmoll
Copy link
Contributor

mmoll commented May 16, 2017

Whatever puppetlabs-apache is providing could be re-used, but prestarting the Rails app also needs to continue to work.

@vollmerk
Copy link
Author

Easy - but not slick

  • Distinct Variables for Apache Listen lines?

Harder, but 'slicker'

  • Regex-split server port into two variables IP & Port allowing the pre-start code to still work

@ekohl
Copy link
Member

ekohl commented May 16, 2017

I'm not sure what you're trying to do is supposed to work. If I read the code of apache::vhost correct then it should generate the correct apache::listen based on the IP + port so injecting an IP + port combo into $port will break certain use cases. If you want to bind a specific IP then we have the $listen_on_interface parameter but I will agree that it's a bad parameter and we should support the direct IP as well. I'd prefer exposing an explicit IP parameter over splitting a port.

@vollmerk
Copy link
Author

@adamundefined - Can you take a crack at this, when you get a chance?

@mmoll
Copy link
Contributor

mmoll commented Jun 11, 2017

what's the status here?

@Zugschlus
Copy link

I need that functionality as well, preferrably as a list of IP addresses so that 127.0.0.1 can be explicitly included. I am not the original poster, but what exactly what is this issue waiting from the contributor?

Greetings
Marc

@vollmerk
Copy link
Author

Yeah, also who is the contributor? do you mean reporter (aka me?)

@mmoll
Copy link
Contributor

mmoll commented Apr 13, 2018

@vollmerk after your second comment I had the impression you'd work on it, but I'll remove the label then.

Pull requests welcome. :)

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

No branches or pull requests

4 participants