9e09399087
Xray-core: More robust browser header masquerading (chrome, firefox, edge) ( #5802 )
...
Fixes https://github.com/XTLS/Xray-core/issues/5800
2026-03-21 12:24:08 +00:00
0ac13bd910
XHTTP transport: Bugfixes for obfuscations ( #5720 )
...
https://github.com/XTLS/Xray-core/pull/5720#issuecomment-4016290343
2026-03-07 12:34:41 +00:00
b7a22c729b
Xray-core: Dynamic Chrome User-Agent for all HTTP requests by default (overwriteable through config) ( #5658 )
...
https://github.com/XTLS/Xray-core/issues/4996#issuecomment-3855274627
https://github.com/XTLS/Xray-core/pull/5658#issuecomment-3857332687
---------
Co-authored-by: RPRX <63339210+RPRX@users.noreply.github.com >
Co-authored-by: Fangliding <63339210+Fangliding@users.noreply.github.com >
2026-02-06 01:42:31 +00:00
5b849d51a9
XHTTP transport: New options for bypassing CDN's detection ( #5414 )
...
Usage: https://github.com/XTLS/Xray-core/pull/5414#issuecomment-3770071786
Closes https://github.com/XTLS/Xray-core/issues/4346
---------
Co-authored-by: 风扇滑翔翼 <Fangliding.fshxy@outlook.com >
2026-01-31 13:34:13 +00:00
e7c72c011f
XHTTP server: Fix ScStreamUpServerSecs' non-default value ( #5486 )
2026-01-05 01:07:00 +00:00
e466b0497c
DNS DoH: Use Chrome's fingerprint & keepAlivePeriod, Add header padding by default
...
https://github.com/XTLS/Xray-core/discussions/4430#discussioncomment-12374292
2025-03-03 14:45:12 +00:00
c5de08bea6
XHTTP client: Revert "Add back minimal path padding for compatibility"
...
Reverts https://github.com/XTLS/Xray-core/commit/efdc70fbf782433689dcb114e37426395100614d
2025-02-18 11:11:36 +00:00
efdc70fbf7
XHTTP client: Add back minimal path padding for compatibility
...
It should be reverted in the future.
2025-01-30 10:45:12 +00:00
ca9a902213
XHTTP server: Add scStreamUpServerSecs, enabled by default ( #4306 )
...
Fixes https://github.com/XTLS/Xray-core/discussions/4113#discussioncomment-11682833
2025-01-19 13:32:07 +00:00
14a6636a41
XHTTP client: Move x_padding into Referer header ( #4298 )
...
""Breaking"": Update the server side first, then client
2025-01-18 12:05:19 +00:00
ce6c0dc690
XHTTP XMUX: Abandon client if client.Do(req) failed ( #4253 )
...
https://github.com/XTLS/Xray-core/commit/51769fdde1ca663dcb08d942618e480bee13109f
2025-01-06 14:06:11 +00:00
4ce65fc74c
XHTTP XMUX: cMaxLifetimeMs -> hMaxReusableSecs, Refactor default values
...
"xmux": {
"maxConcurrency": "16-32",
"maxConnections": 0,
"cMaxReuseTimes": 0,
"hMaxRequestTimes": "600-900",
"hMaxReusableSecs": "1800-3000",
"hKeepAlivePeriod": 0
}
Fixes https://github.com/XTLS/Xray-core/discussions/4113#discussioncomment-11685057
2024-12-31 10:00:19 +00:00
73e0d4a666
XHTTP XMUX: Add hMaxRequestTimes and hKeepAlivePeriod ( #4163 )
...
Fixes https://github.com/XTLS/Xray-core/discussions/4113#discussioncomment-11492833
2024-12-15 05:43:10 +00:00
8cd9a74376
XHTTP client: Refactor "packet-up" mode, chasing "stream-up" ( #4150 )
...
* Add wroteRequest (waiting for new quic-go)
* Use XTLS/quic-go instead
* Client doesn't need `scMaxConcurrentPosts` anymore
* GotConn is available in H3
* `scMaxConcurrentPosts` -> `scMaxBufferedPosts` (server only, 30 by default)
Fixes https://github.com/XTLS/Xray-core/issues/4100
2024-12-11 14:05:39 +00:00
acbf36e21b
SplitHTTP server: Add global CORS headers for browser dialer ( #3830 )
2024-09-20 09:55:54 +02:00
b1c6471eeb
SplitHTTP client: Add xmux (multiplex controller) for H3 & H2 ( #3613 )
...
https://github.com/XTLS/Xray-core/pull/3613#issuecomment-2351954957
Closes https://github.com/XTLS/Xray-core/issues/3560#issuecomment-2247495778
---------
Co-authored-by: mmmray <142015632+mmmray@users.noreply.github.com >
2024-09-16 12:42:01 +00:00
a3b306aaa4
SplitHTTP: Replace responseOkPadding with xPaddingBytes ( #3643 )
2024-08-10 21:47:42 +00:00
4b7947cca9
SplitHTTP server: add ok padding ( #3614 )
2024-08-02 03:16:19 +02:00
30af792777
SplitHTTP: Rename three options & Reduce server defaults ( #3611 )
...
* maxUploadSize -> scMaxEachPostBytes, default is 1MB on both sides (was 2MB on the server)
* minUploadIntervalMs -> scMinPostsIntervalMs, default is 30ms on the client (no server support for now)
* maxConcurrentUploads -> scMaxConcurrentPosts, default is 100 on both sides (was 200 on the server)
2024-07-29 10:10:29 +00:00
33daa0c94b
SplitHTTP: Fix wrong config deserialization ( #3610 )
...
Testing was conducted only using explicit parameters, and using
testsuite. However, when the parameters are not explicitly set in JSON
config, it seems that `c.MaxUploadSize` will contain `RandRangeConfig {
From: 0, To: 0 }` instead of `nil`, which breaks upload entirely.
2024-07-29 08:50:59 +00:00
59f6685774
SplitHTTP: More range options, change defaults, enforce maxUploadSize, fix querystring behavior ( #3603 )
...
* maxUploadSize and maxConcurrentUploads can now be ranges on the client
* maxUploadSize is now enforced on the server
* the default of maxUploadSize is 2MB on the server, and 1MB on the client
* the default of maxConcurrentUploads is 200 on the server, and 100 on the client
* ranges on the server are treated as a single number. if server is configured as `"1-2"`, server will enforce `2`
* querystrings in `path` are now handled correctly
2024-07-29 04:35:17 +00:00
8a4217fdf5
SplitHTTP client: Add minUploadInterval ( #3592 )
2024-07-27 12:52:36 +00:00
c10bd28731
Add SplitHTTP Transport ( #3412 )
2024-06-18 05:36:36 +00:00
Lumière Élevé