[Feat]: Ability to set proxied ports to public #6008

What is your suggestion?

Set proxied port visibility to either public or private. When a port is set to public, cookie-based authentication is disabled, even if the auth is set to password.

In GitHub Codespaces, the feature looks like this:

Why do you want this feature?

Useful for developing with 3rd party integrations that call your API (e.g. webhooks, Slack or Discord bots)

Are there any workarounds to get this functionality today?

What I currently do is I turn off authentication in code-server, then I do authentication at the reverse proxy level instead, which lets me turn off authentication based on paths. So all paths that match the specified proxy are not authenticated.

This works but is not amazing because either all ports are public or all ports are private; I can't mix the two.

Are you interested in submitting a PR for this?

Not really, the workaround is acceptable for my current use-case