mmmray 2becdd6414
SplitHTTP server: Fix panic during concurrent Close and Push (#3593)
When Close and Push are called concurrently, it may happen that Push attempts to write to an already-closed channel, and trigger a panic.

From a user perspective, it results in logs like this:

    http: panic serving 172.19.0.6:50476: send on closed channel

It's probably triggered when download is closed at the same time an upload packet is submitted.

These panics don't crash the server and the inbound is still usable.
2024-07-26 04:36:55 +02:00
2024-07-12 00:20:06 +02:00
2024-07-15 14:04:04 +02:00
2024-07-21 21:32:26 +00:00
2024-06-29 14:32:57 -04:00
2024-07-09 12:19:31 -04:00
2024-07-12 00:20:06 +02:00
2024-07-12 00:20:06 +02:00
2024-06-03 16:40:13 -04:00
2024-07-17 13:45:16 +00:00
2024-07-17 13:45:16 +00:00
2020-11-25 19:01:53 +08:00
2024-07-12 00:20:06 +02:00
2024-07-15 13:53:43 +00:00

Project X

Project X originates from XTLS protocol, providing a set of network tools such as Xray-core and REALITY.

README is open, so feel free to submit your project here.

License

Mozilla Public License Version 2.0

Documentation

Project X Official Website

Telegram

Project X

Project X Channel

Installation

Usage

GUI Clients

Others that support VLESS, XTLS, REALITY, XUDP, PLUX...

Contributing

Code of Conduct

Credits

Compilation

Windows (PowerShell)

$env:CGO_ENABLED=0
go build -o xray.exe -trimpath -ldflags "-s -w -buildid=" ./main

Linux / macOS

CGO_ENABLED=0 go build -o xray -trimpath -ldflags "-s -w -buildid=" ./main

Reproducible Releases

make

Stargazers over time

Stargazers over time

Description
Languages
Go 99.6%
HTML 0.2%
Shell 0.1%