Cockpit master now listens on port 1001

Stephen Gallagher sgallagh at redhat.com
Tue May 6 11:56:30 UTC 2014


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue 06 May 2014 07:50:46 AM EDT, Stef Walter wrote:
> On 06.05.2014 13:43, Stephen Gallagher wrote:
>> On 05/06/2014 07:19 AM, Andreas Nilsson wrote:
>>> On 05/06/2014 11:29 AM, Marius Vollmer wrote:
>>>> Hi,
>>>> 
>>>> we just changed the port that Cockpit listens on by default.
>>>>  It's just nicer.
>> 
>>> Very much indeed! This will make it a lot easier to remember 
>>> what to dial in to.
>> 
>> Looks like 1001 is not registered to any known service[1]. 
>> Probably would be a good idea to contact IANA and get this made 
>> official.
> 
> Would that work? Or would we just be treated as a website, and told
> to go port 80?


No, I think it makes perfect sense to have a separate address for a
management service. We don't necessarily have to reserve it for
Cockpit alone, but perhaps requisition it for "HTTP-based system
management consoles".

Multiplexing port 80 is a hack of the worst kind and I think we can
make that argument.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1
Comment: Using GnuPG with Thunderbird - http://www.enigmail.net/

iEYEARECAAYFAlNoze4ACgkQeiVVYja6o6NNHACfUt84G2xuomcURYNZSPr4OMew
OjgAnRMbKethREOSJiGwpJm8l4i/07DC
=CnUA
-----END PGP SIGNATURE-----


More information about the cockpit-devel mailing list