Phus Lu
Phus Lu
We have a big service (up to 50 edge servers) which use fasthttp as frontend, the peak of total QPS reach 500K every day. We are comforted with fasthttp worker...
a possible path is 1. rewrite `fasthttp.ErrDialTimeout` to a struct, maybe `DailTimeoutError` which implement `net.Error` interface ```golang // see https://golang.org/src/net/net.go?s=17034:17068#L539 type DailTimeoutError struct { Err string Addr string } func...
`string(v.GetStringBytes())` will do a memory copy. I think add "GetString" is not a good idea, we shall keep GetStringBytes and let users choose use `b2s()` or `string()` in their usecases.
should be related with tls session ticket issue, we're working on it.
hard to fix in nginx layer, I'm re-writing patches and migrate ja3 logic into openssl layer. see https://github.com/phuslu/nginx-ssl-fingerprint/tree/re/patches
should fixed in master branch. please take a look @fkasler @paragor
1st is intended currently, but still in discussion and may change in future. 2nd seems a bug, will look today.
refactor patches in master (should be more performant), now the `extensions` difference is fixed. for the crash/segfault issue, let me add some guard code to fix it. @paragor thanks for...
Aligened internally and disabled the "tls1.3 fixup" in nginx patch. Now the version should be "ok" Personally i don't think it is "wrong" version but we want re-use existing ja3...
Thanks and no need rush, i still need to add some guard code, like https://github.com/phuslu/nginx-ssl-fingerprint/commit/06fb0a65ee813c401532573b04d108052cde37cf