schneems 0584a3345e [close #1327] Fix double port bind in Rails ... The "default" configuration puma level is initialized with a "binds" of `tcp://0.0.0.0:9292`. Puma is designed to be able to bind to multiple ports. When a `:port` is sent from Rails along with an empty `user_supplied_options` then the port is treated as a "default". This is merged in with the system defaults, and then later converted into a "binds" via calling `config.port` in the `set_host_port_to_config` method. The bug comes due to the "level" of the configuration. Since both are being set on the same "level" the `port` call does not over-write the existing binds but instead prepends to the array. We can fix by ensuring that any binds in a given "level" are empty before setting it.		2017-08-02 14:28:39 -05:00
..
puma	[close #1327] Fix double port bind in Rails	2017-08-02 14:28:39 -05:00
rack/handler	[close #1327] Fix double port bind in Rails	2017-08-02 14:28:39 -05:00
puma.rb	Require StateFile if needed.	2016-09-08 17:46:24 +02:00