manage runserver does not allow host name as address

[Karmel Allison]

In Django 1.2, it was possible to use a host name (i.e., example.com) to run a Django server from manage.py:

python manage.py runserver example.com:8000

However, that convenience has been removed in Django 1.3-alpha. It looks like in order to add functionality for IPv6 addresses, a regex was added (​r14711, line 12) that raises an error if non-IP-like addresses are used:

python manage.py runserver example.com:8000
Error: 'example.com:8000' is not a valid port numberor address:port pair.

The ability to run the server using host names was quite convenient, and preferable in many cases to having an IP specified. Would it be possible to re-enable that feature?

Thanks!

[rasca]

I can confirm the behavior. Accepting the ticket.

This should be fixed before releasing 1.3.

[Jannis Leidel]

Not really a regression since it was not only undocumented but also clearly defined as a IP:port pair

[Claude Paroz]

I've also a use case where I need to provide a FQDN to runserver (handling of various subdomains in an app). I do not see the real advantage of using the regex instead of the simpler (r)split that was previously used. The addr part of the 'addr:port' sequence is my business, not Django's.

[Claude Paroz]

Allow FQDN in addr part of runserver

[Łukasz Rekucki]

I used a regex, because I needed a simple way to distinguish between IPv4 and IPv6. I think splitting on ":" is confusing as it's also an IPv6 address separator. I also wanted to give the user more meaningful error messages.

[Łukasz Rekucki]

Alternative patch, that accepts ASCII hostnames.

[Jannis Leidel]

Yah, lrekuck's patch seems to work nicely.

[Claude Paroz]

Patch of lregucki with basic tests

[Russell Keith-Magee]

(In [15215]) Fixed #14928 -- Ensure that a fully qualified domain name can be used for runserver. Thanks to Karmel Allison for the report, Łukasz Rekucki for the patch, and claudep for the tests.

[Jacob]

Milestone 1.3 deleted