possible to include this ctx.Response.Header.SetContentEncodingBytes <- ?

[kolinfluence]

just this will do.

ctx.Response.Header.SetContentEncodingBytes 

the rest can work around. thx

[kolinfluence]

after 2 weeks of workarounds, i'm finally left with this last part. seemed a lot of "missing" compatibility features but can be fixed no issue. great work guys. i think mostly a lot of copying and pasting needed.

pls help with this last section as the rest i've already figured out how to workaround checking the codes. only this last section is not evident. thx!

[kolinfluence]

@li-jin-gou can i buy u a coffee when this and #428 is resolved as token of appreciation?

thx a lot for the help extended so far here, on fasthttp and fiber.

[li-jin-gou]

just this will do.

ctx.Response.Header.SetContentEncodingBytes 

the rest can work around. thx

Hertz does not currently support this feature, you can use ctx.Response.Header.Set.

[li-jin-gou]

@li-jin-gou can i buy u a coffee when this and #428 is resolved as token of appreciation?

thx a lot for the help extended so far here, on fasthttp and fiber.

This is not necessary, as far as I know, you are the first person to use the Hertz HTTP2 feature in open-souece and we appreciate your trust in Hertz.

[li-jin-gou]

Same as valyala/fasthttp#1311 and I think we can also support it.

[wang-tsh]

Please assign me.

[li-jin-gou]

Please assign me.

thanks

[wang-tsh]

Please assign me.

thanks

my pleasure