zino7825
zino7825
I've same experienced after upgrade java from 8 to 11.
> It's difficult to understand fully the behavior of browsers with QUIC. In my experience, chromium was more restrictive, as it seems to only accept certificates signed by an authority...
> > but I can access google.com with http3 on current browser. > > Just like mine used to work on quic.cloudflare.com while not on haproxy.org, and recently started to...
@wtarreau I got it. I tried to set quic-force when starting chrome ( chrome --enable-quic --origin-to-force-quic-on=xxx.com:443 ) and I checked that h3 protocol was succeed. it's really weird things. -_-;...
I found the problem. If the string type is used, only one table raw is maintained. ``` ## add acl : path_beg /Articlexxx for traking This stick-table store type is...
@wtarreau What you mean is that the "Base32+src and storage type string" combination can be a problem? What's unusual is that there's no problem with other domains, but only this...
@wtarreau we've never this happened before upgrade 2.5.x. we also upgraded openssl to version 1.1.1o.
Spoa is a really necessary function, so you need to think about next negation. We are using so many different types of spoa. Authentication module, mirroring, mod_security, etc.. I think...
@Darlelet Wow!! I didn't know that. thx!! Please make backport to 2.8.x too!!
@git001 I've checked that ocsp, ocsp-stapling, ocsp-stapling are enabled after wolfssl build. I guess that wolfssl contains ocsp but seems to be unable to utilize ocsp function of wolfssl in...