[PR #5253] [CLOSED] web/frps: restore XTCP support across dashboard views #5207

New issue

Closed

opened 2026-05-05 14:56:42 -06:00 by gitea-mirror · 0 comments

gitea-mirror commented

2026-05-05 14:56:42 -06:00

Owner

📋 Pull Request Information

Original PR: https://github.com/fatedier/frp/pull/5253
Author: @Daijunfan
Created: 3/20/2026
Status: ❌ Closed

Base: dev ← Head: fix/frps-xtcp-dashboard-support

📝 Commits (1)

cf99f1f web/frps: restore XTCP handling across dashboard views

📊 Changes

4 files changed (+28 additions, -1 deletions)

View changed files

📝 web/frps/src/utils/proxy.ts (+8 -0)
📝 web/frps/src/views/ClientDetail.vue (+13 -1)
📝 web/frps/src/views/Proxies.vue (+4 -0)
📝 web/frps/src/views/ProxyDetail.vue (+3 -0)

📄 Description

Summary

restore XTCP handling in the frps dashboard proxy list by adding the missing xtcp tab and list mapping
include XTCP proxies in client detail aggregation so they show up alongside the other proxy types
add an XTCPProxy frontend model and use it consistently in proxy detail handling instead of falling back to BaseProxy

Why

The backend API already supports XTCP, and ProxyDetail.vue even has XTCP-specific visual treatment, but the current web/frps UI still misses explicit XTCP handling in its main entry points. As a result, XTCP proxies are omitted from:

the global Proxies view
the per-client proxy list
the explicit typed model path in the proxy detail view

This restores end-to-end dashboard support for XTCP instead of only patching a single tab.

Closes #5244.

Verification

uploaded the updated web/ workspace to an Ubuntu 22.04 cloud host and ran npm ci from web/
ran npm run type-check in web/frps
ran npm run build in web/frps

_{🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.}

## 📋 Pull Request Information **Original PR:** https://github.com/fatedier/frp/pull/5253 **Author:** [@Daijunfan](https://github.com/Daijunfan) **Created:** 3/20/2026 **Status:** ❌ Closed **Base:** `dev` ← **Head:** `fix/frps-xtcp-dashboard-support` --- ### 📝 Commits (1) - [`cf99f1f`](https://github.com/fatedier/frp/commit/cf99f1f13bec46f209e6fcc0cfd731a1213fca30) web/frps: restore XTCP handling across dashboard views ### 📊 Changes **4 files changed** (+28 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `web/frps/src/utils/proxy.ts` (+8 -0) 📝 `web/frps/src/views/ClientDetail.vue` (+13 -1) 📝 `web/frps/src/views/Proxies.vue` (+4 -0) 📝 `web/frps/src/views/ProxyDetail.vue` (+3 -0) </details> ### 📄 Description ## Summary - restore XTCP handling in the frps dashboard proxy list by adding the missing `xtcp` tab and list mapping - include XTCP proxies in client detail aggregation so they show up alongside the other proxy types - add an `XTCPProxy` frontend model and use it consistently in proxy detail handling instead of falling back to `BaseProxy` ## Why The backend API already supports XTCP, and `ProxyDetail.vue` even has XTCP-specific visual treatment, but the current `web/frps` UI still misses explicit XTCP handling in its main entry points. As a result, XTCP proxies are omitted from: - the global Proxies view - the per-client proxy list - the explicit typed model path in the proxy detail view This restores end-to-end dashboard support for XTCP instead of only patching a single tab. Closes #5244. ## Verification - uploaded the updated `web/` workspace to an Ubuntu 22.04 cloud host and ran `npm ci` from `web/` - ran `npm run type-check` in `web/frps` - ran `npm run build` in `web/frps` --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>