No, it is definitely getting back a 403 from the server:

    HTTP/2 403 Forbidden
    retry-after: 0
    content-type: text/plain
    accept-ranges: bytes
    date: Fri, 14 Jan 2022 19:10:51 GMT
    via: 1.1 varnish
    cache-control: private, max-age=3600
    strict-transport-security: max-age=31536000; includeSubdomains
    x-content-type-options: nosniff
    x-frame-options: SAMEORIGIN
    x-xss-protection: 1; mode=block
    server: snooserv
    x-clacks-overhead: GNU Terry Pratchett
    content-length: 7
    X-Firefox-Spdy: h2