https://discord.cloudflare.com logo
Join Discord
Powered by
# r2
  • z
    that wouldn't explain why I always get h2 in chrome and 1.1 in curl
  • h
    Inter-CF communications don't use HTTP, afaik.
  • h
    So whether or not a DO has it, the fact that the Edge connection supports it means it should be higher
  • s
    Fwiw it is planned
  • a
    oh when using curl, we should probably spoof a chrome useragent
  • a
    although nvm, the decision would need to be made before then i guess
  • s
    I've previously raised an issue about the PCI compliance problems with not having minimum TLS settings respected, and I was told that in the not too distant future, these zone features will be inherited
  • k
    That's great to hear
  • z
    🔲 make r2 work as expected (requires enterprise plan)
  • e
    https://static.brickadia.com/resources/ uses http/2 to serve its 404 page
  • a
    huh, for me it doesn't
  • k
    I'm not able to get an HTTP/2 response for that using cURL
  • k
    Maybe it's Chrome being silly by saying it "offered" H2
  • z
    is there any sense to this theory
  • a
    hmm, i feel it would say h2 a lot more if that were the case
  • e
  • e
    i do have warp on though 🤔
  • z
    server accepted h2
    big think
  • e
    oh ok it doesnt do it with warp off
  • z
    none of us get that in curl
  • e
    good to know
  • k
    Why would it behave differently on Warp? Warp isn't a proxy, right?
  • e
    you can enable tls decryption
  • e
    the hint is
    Copy code
    *  issuer: C=US; ST=California; L=San Francisco; O=Cloudflare, Inc.; OU=Gateway Intermediate ECC Certificate Authority
  • e
    and honestly it was my bad for not checking that
  • k
    Ah
  • a
    i get a different 
    SSL connection using TLSv1.3 / TLS_AES_256_GCM_SHA384
  • e
    yeah 👍
  • e
    its more sensible and http 1.1 after fixing that
  • a
    why chrome is showing h2 being used for @Zeblote is still a mystery i believe
1...901902903...1050Latest