#851 ✓wontfix

Play doesn't listen on multiple ports

Reported by Arthur | May 18th, 2011 @ 08:28 PM | in 1.2.5 (closed)

Framework version: 1.2.1
Platform you're using: Linux

Reproduction steps:
1. Create a new Play application
2. Try to have it listen for HTTP requests on both port 9000 and 9001.

There is no way in the Play framework to listen for requests on more than one port. I propose that Play accept a comma seperated list of possible ports as the value of http.port in application.conf.

The need for this arrose for me when doing some web development at work. I used Play to create a webservice that listened for requests and it also provided a user interface at port 80. The specification soon changed and the webservice had to listen on a different port to 80, but users would still expect to visit port 80. I've fixed this in my Play fork: https://github.com/aembleton/play and am raising this so that I can submit a pull request into the main play fork. My pull request: https://github.com/playframework/play/pull/100

Comments and changes to this ticket

Please Sign in or create a free account to add a new ticket.

With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.

New-ticket Create new ticket

Create your profile

Help contribute to this project by taking a few moments to create your personal profile. Create your profile »

<h2>Play framework</h2>

Play makes it easier to build Web applications with Java. It is a clean alternative to bloated Enterprise Java stacks. It focuses on developer productivity and targets RESTful architectures. Learn more on the <a href="http://www.playframework.org">http://www.playframework.org</a> website.<br><br>

<h2>Source code is hosted on github</h2>Check out our repository at <a href="http://github.com/playframework/play">http://github.com/playframework/play</a><br><br>

<h2>Contributing, creating a patch</h2> Please read the <a href="http://play.lighthouseapp.com/projects/57987/contributor-guide">contributor guide</a><br><br>

<h2>Reporting Security Vulnerabilities</h2> Since all bug reports are public, please report any security vulnerability directly to <em>guillaume dot bort at gmail dot com</em>.<br><br>

<h2>Creating a bug report</h2> Bug reports are incredibly helpful, so take time to report bugs and request features in our ticket tracker. We’re always grateful for patches to Play’s code. Indeed, bug reports with attached patches will get fixed far quickly than those without any.<br><br>

Please include as much relevant information as possible including the exact framework version you're using and a code snippet that reproduces the problem.<br><br>

Don't have too much expectations. Unless the bug is really a serious "everything is broken" thing, you're creating a ticket to start a discussion. Having a patch (or a branch on Github we can pull from) is better, but then again we'll only pull high quality branches that make sense to be in the core of Play.

People watching this ticket

Referenced by