coder / coder/code-server

[Feat]: Ability to set proxied ports to public

未关闭
#6,008 1 条评论 8 个 reaction 已指派 0 人 在 GitHub 查看
enhancement
主要语言
TypeScript
星标
79.3k
派生
6.8k
平均合并
2 天 6 小时
30 天内合并 PR
41

描述

## 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:

![image](https://user-images.githubusercontent.com/37142182/217548692-e58bdc52-f8fa-4817-b814-f0920aafc3b1.png)

## 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

贡献指南

打开贡献指南

评估

这个 Issue 还没有评估数据。

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。