11 Commits (0e2304c403bf2c032d204e45b76e8b61423ae244)

Author	SHA1	Message	Date
zonescape	83bab5dd90	Chore: Run gofmt (#3990)	2024-11-09 11:16:11 +00:00
yuhan6665	079d0bd8a9	Refactor log (#3446) ... * Refactor log * Add new log methods * Fix logger test * Change all logging code * Clean up pathObj * Rebase to latest main * Remove invoking method name after the dot	2024-06-29 14:32:57 -04:00
A1lo	10d6b06578	fix(transport): correctly release UDS locker file (#2305) ... * fix(transport): correctly release UDS locker file * use callback function to do some jobs after create listener	2023-08-26 07:35:44 -04:00
Hirbod Behnam	526c6789ed	Add custom path to gRPC (#1815)	2023-03-26 09:28:19 +03:30
RPRX	55dc26f228	Add REALITY support to gRPC client and server ... Now you are able to configure REALITY gRPC client and server Duplicate of REALITY H2, perhaps, just for fun	2023-02-27 19:52:01 +00:00
世界	f046feb9ca	Reformat code	2022-05-18 15:29:01 +08:00
yuhan6665	c4fc277758	add comment for gRPC TLS silent failure behavior (#779) ... When gRPC transport have been configured to use TLS, it may silently ignore TLS failure. This may make it harder to diagnose TLS setting issues when gRPC transport is used. This comment is added to help other developers be aware of this caveat. Co-authored-by: Shelikhoo <xiaokangwang@outlook.com>	2021-10-22 12:38:40 +08:00
Arthur Morgan	c950edede2	Merge pull request #618 from XTLS/fix/service-name ... gRPC: Use `PathEscape` encoded service name	2021-09-08 00:53:55 +08:00
hmol233	57b9006d26	gRPC: add keepalive option for server	2021-07-05 21:25:03 +08:00
hmol233	3dc9fba20d	gRPC: Use `PathEscape` encoded service name	2021-06-27 16:46:26 +08:00
RPRX	a0a32ee00d	Add gRPC Transport support (#356) ... Co-authored-by: JimhHan <50871214+JimhHan@users.noreply.github.com>	2021-03-14 15:02:07 +00:00