Closed sshock closed 3 months ago
Good catch, ty for reporting it! Is this a documentation bug only, or does it affect some functionality you're looking to wire up?
As far as I know it's just a documentation bug. I've been able to decode header frames no problem, both on the client and on the server side.
In the
HTTP2::Header::Decompressor
class it has this comment:Yet the constructor does not take any normal arguments, just an options hash:
So if you try to initialize it as described, you'll get a
wrong number of arguments
error.