fix(outbound): add None option to uTLS fingerprint in TLS form (#4760)
Some checks are pending
CI / go-test (push) Waiting to run
CI / govulncheck (push) Waiting to run
CI / frontend (push) Waiting to run
CodeQL Advanced / Analyze (go) (push) Waiting to run
CodeQL Advanced / Analyze (actions) (push) Waiting to run
CodeQL Advanced / Analyze (javascript-typescript) (push) Waiting to run
Release 3X-UI / build (386) (push) Waiting to run
Release 3X-UI / build (amd64) (push) Waiting to run
Release 3X-UI / build (arm64) (push) Waiting to run
Release 3X-UI / build (armv5) (push) Waiting to run
Release 3X-UI / build (armv6) (push) Waiting to run
Release 3X-UI / build (armv7) (push) Waiting to run
Release 3X-UI / build (s390x) (push) Waiting to run
Release 3X-UI / Build for Windows (push) Waiting to run

Hysteria doesn't use uTLS, but the outbound TLS form's uTLS dropdown only listed concrete fingerprints (chrome, firefox, ...) with no explicit empty entry. Add a None option, matching the inbound TLS form, so the fingerprint can be left empty.
This commit is contained in:
MHSanaei 2026-06-01 19:21:37 +02:00
parent 803e010921
commit 6ae1b38607
No known key found for this signature in database
GPG key ID: 7E4060F2FBE5AB7A

View file

@ -20,7 +20,7 @@ export default function TlsForm() {
<Select
allowClear
placeholder={t('none')}
options={UTLS_OPTIONS}
options={[{ value: '', label: t('none') }, ...UTLS_OPTIONS]}
/>
</Form.Item>
<Form.Item