From 9f84859ff60047f989f1a6bfb839ea49d4c5c29a Mon Sep 17 00:00:00 2001 From: MHSanaei Date: Tue, 26 May 2026 14:12:29 +0200 Subject: [PATCH] feat(frontend): outbound TCP HTTP camouflage parity with inbound Add method/version inputs, request header map, and full response sub-section (version/status/reason/headers) to OutboundFormModal so the outbound side can configure the same HTTP-1.1 obfuscation knobs the inbound side already exposed. --- frontend/src/pages/xray/OutboundFormModal.tsx | 77 +++++++++++++++++-- 1 file changed, 70 insertions(+), 7 deletions(-) diff --git a/frontend/src/pages/xray/OutboundFormModal.tsx b/frontend/src/pages/xray/OutboundFormModal.tsx index 5f95f630..0a472f61 100644 --- a/frontend/src/pages/xray/OutboundFormModal.tsx +++ b/frontend/src/pages/xray/OutboundFormModal.tsx @@ -1136,7 +1136,12 @@ export default function OutboundFormModal({ path: ['/'], headers: {}, }, - response: undefined, + response: { + version: '1.1', + status: '200', + reason: 'OK', + headers: {}, + }, } : { type: 'none' }, ) @@ -1145,12 +1150,24 @@ export default function OutboundFormModal({ {type === 'http' && ( <> - {/* Host is stored as a string[] on the - wire (V2 header map: { Host: [...] }). - The form-level normalize/getValueProps - translate to/from a comma-joined input - so the user types one Host:contentReference[oaicite:0]{index=0} value per - server they want camouflaged. */} + + + + + + + + + + + + + + + + + + + + + + )}