search

nspcc-dev / status-fs-neo-org

NeoFS status monitoring page
https://status.fs.neo.org/
GNU General Public License v3.0
0 stars 0 forks source link

use default ports for neogo endpoints #110

Closed 532910 closed 3 months ago

532910 commented 4 months ago

port is not required more

carpawell commented 3 months ago

Missing ports looks like smth that should return some HTML page to me. I feel it weird, do you have some common examples when a public service allows skipping port specifying?

532910 commented 3 months ago

let's do it vice versa: do you have some common examples when a public service port must be specified?

AnnaShaleva commented 3 months ago

Vote down from my side, status.fs is the last source of truth for me to check on various ports of our nodes.

carpawell commented 3 months ago

@532910, i meant some services that are not REST. I thought about it like e.g. about a mail server. However, i have thought about it one more time and maybe JSON RPC is closer to a "public HTTP API" than i thought. IDK, i am kinda neutral.

532910 commented 3 months ago

status.fs is the last source of truth for me to check on various ports of our nodes.

what exactly would you like to check and why do you need it?

roman-khimov commented 3 months ago

We don't have a clear agreement on the need of this change. But we have a tradition and well-known port numbers for P2P-HTTP-HTTPS services that are expected from the node. These ports are being used, that's what services listen to, so it's OK to have these ports exposed to the public. Therefore, NACK on this one.