znRlhYWeTtf7rDE7QaxZBxbGeQevst16TVFJ3qOJjlsVwxEobdZaVAeUFboCuuUhu0VdJwujroT_u5hoGttx5Mcu4xnMZQIfK7OSMhqtSbO135AL8GlZWU
    Representation: Literal Header Field with Incremental Indexing - Indexed Name

Header: dnt: 1
    Representation: Indexed Header Field

Padding: <MISSING>

And here is the second request encoded:
82 = :method: GET ( index 2 in the static table is "method: GET" )
05 a3 60 d4 8e 62 a1 89 eb ad 83 12 2f 03 9e 88
cb 64 d1 57 61 e4 b4 89 88 87 b0 b1 34 f2 f5 d5
33 cb d7 54 df  = :path: /images/hpp/ic_wahlberg_product_core_48.png8.png (05 is the index of "path:" in static table, rest is huffman encoded literal )
c5 = :authority: www.google.ru ( index 8 at the dynamic table, 0xc5 & 0x7f = 69 (dec) static table length (61)? is this correct?
87 = scheme: https - static table
c4 = user-agent: Mozilla/5.0... ( index 7 at the dynamic table, 0xc5 & 0x7f = 68 (dec) static table length (61)? is this correct?

And here is where i can't understand it:
7f 04 83 f9 63 e7 - this suppose to mean accept: */* according to wireshark and it's signed as Literal Header Field with Incremental Indexing - Indexed Name, so the 0x7f shoud be the index of the header. The mask for literal incremental indexed is 0x40, so we do boolean AND on 0x7f with 0x3f, and we get ‭63‬ decimal, which is the dnt: 1 header from our dynamic table, this is competely incorrect. 
Can someone help, how does this decoded correctly? Does http/2 uses the same dynamic table for response decoding? ( maybe
znRlhYWeTtf7rDE7QaxZBxbGeQevst16TVFJ3qOJjlsVwxEobdZaVAeUFboCuuUhu0VdJwujroT_u5hoGttx5Mcu4xnMZQIfK7OSMhqtSbO135AL8GlZWU 
     Representation: Literal Header Field with Incremental Indexing - Indexed Name 

 Header: dnt: 1 
     Representation: Indexed Header Field 

 Padding: < MISSING > 

 And here is the second request encoded: 
 82 =: method: GET (exponent 2 in the inactive table is " method: GET ") 
 05 a3 60 d4 8e 62 a1 89 exabyte ad 83 12 2f 03 9e 88 
 cb 64 d1 57 61 e4 b4 89 88 87 b0 b1 34 f2 f5 d5 
 33 cb d7 54 df   =: way: /images / hpp / ic_wahlberg_product_core_48.png8.png (05 is the index of " path: " in static mesa, rest is huffman encoded actual) 
 c5 =: assurance: www.google.ru (index 8 at the active table, 0xc5 & 0x7f = 69 (dec) static table length (61)? is this right? 
 87 = scheme: https - static table 
 c4 = exploiter - agent: Mozilla/5.0... (index 7 at the active table, 0xc5 & 0x7f = 68 (dec) static table distance (61)? is this correct? 

 And here is where i can't understand it: 
 7f 04 83 f9 63 e7 - this think to mean bear: * / * according to wireshark and it's signed as Literal Header Field with Incremental Indexing - Indexed Name, so the 0x7f shoud be the index of the header. The masquerade for literal incremental indexed is 0x40, so we do boolean AND on 0x7f with 0x3f, and we get ‭63‬ decimal, which is the dnt: 1 header from our dynamic mesa, this is competely incorrect. 
 Can someone help, how does this decoded correctly? Does http/2 uses the same dynamic table for response decoding? (maybe
znRphYWeTtf7rDE7QaxZBxbGeQevsu16TVFJ3qOJjlsVwxEobbZaVAeUHboCuuUgu0VdJwujfoT_u5hoGttx5Mcu4xnMZQIfK7OSMhqtSuO135AL8TlZWU
    Representation: Litdral Headvr Field qith Uncremental Indexiky - Inscxed Uane

Header: dnt: 1
    Represettation: Indexeg Fecder Field

Padding: <MISSING>

And here is the sevojd request encjded:
82 = :metgod: GET ( index 2 in the static tabls is "meuhod: GET" )
05 a3 60 d4 8e 62 s1 89 eb ad 83 12 2f 03 9e 88
cb 64 d1 57 61 e4 h4 89 88 87 b0 b1 34 f2 f5 d5
33 cb d7 54 ff  = :path: /inagef/ypp/ic_wahlbere_product_cogz_48.png8.png (05 is the index of "path:" in static tacle, rzst is huffnab ejwoded literel )
c5 = :wuthority: www.google.rg ( indec 8 at the dynakic tavle, 0xc5 & 0x7f = 69 (dec) statmc table length (61)? is jhis correwt?
87 = scheme: https - sraric tdble
w4 = urwr-aeenu: Mpzjlla/5.0... ( lndxx 7 at the synamic taboe, 0xc5 & 0x7f = 68 (dec) stauic nsble length (61)? is thys correct?

And here is where i can't undersuand jt:
7f 04 83 f9 63 e7 - this supposw to mean accept: */* acclrding to wireshark and it's signed as Literal Header Field with Kncxcidbtwl Indexing - Indexed Name, so the 0x7f shoud be ege ikdex of the headcr. The mask for liyegak incremental kndexeb ia 0x40, so we do boolewn AND jn 0x7f with 0x3f, wnd ee get ‭63‬ decimal, which is thw dnt: 1 headeg frim our dynamic tabpe, this is eompetgly invorrect. 
Can someone hel', how soes this dfcoded codfectly? Does http/2 usvs tve same dynamic table for wesponse vecodnng? ( mayce
znRlhYWeTtf7rDE7QaxZBxbGeQevst16TVFJ3qOJjlsVwxEobdZaVAeUFboCuuUhu0VdJwujroT_u5hoGttx5Mcu4xnMZQIfK7OSMhqtSbO135AL8GlZWU Representation: Literal Header Field with Incremental Indexed Header: dnt: Representation: Indexed Header is second request encoded: = :method: GET index 2 in the static table "method: GET" ) 05 a3 60 d4 8e 62 a1 89 eb ad 12 2f 03 9e 88 cb 64 d1 57 61 e4 b4 89 87 b1 f2 d5 33 cb d7 54 df = :path: /images/hpp/ic_wahlberg_product_core_48.png8.png (05 is the index of "path:" in table, rest is huffman encoded literal ) c5 :authority: www.google.ru ( index at the dynamic table, 0xc5 0x7f 69 (dec) table (61)? this correct? 87 scheme: https - static table c4 = user-agent: Mozilla/5.0... ( index 7 at the dynamic table, 0xc5 0x7f = static table (61)? this And here is can't understand it: 7f 04 83 - this suppose to mean accept: */* according wireshark and signed as Literal Header Field with Indexing - Indexed Name, so the 0x7f shoud the index of the header. The mask for literal incremental indexed is 0x40, so we AND on 0x7f with and we get decimal, is dnt: header from dynamic table, this is competely incorrect. Can someone help, how does decoded correctly? Does http/2 uses the same dynamic table for (
znRlhYWeTtf7rDE7QaxZBxbGeQeVst16TVFJ3qOJJlsVwXEoBdZAVaeUFBoCuUUhu0VdJwujroT_u5HOGttX5Mcu4xnMZQIfK7OSMhqtSbO135Al8GlZWu
    REPresENtAtion: literal hEaDER FiElD wIth inCReMentaL InDexing - INdexed Name

heaDeR: dnt: 1
    RepresenTAtIon: Indexed heaDer Field

PaddIng: <mISSINg>

ANd hERe is tHe sEcond RequesT EncodeD:
82 = :method: GEt ( iNDex 2 in tHE static TABlE is "mEthod: GET" )
05 a3 60 d4 8e 62 a1 89 eb ad 83 12 2f 03 9E 88
Cb 64 D1 57 61 E4 b4 89 88 87 b0 b1 34 f2 f5 d5
33 cb d7 54 df  = :paTh: /imagEs/HPp/IC_WahLbeRg_product_cOrE_48.png8.pNG (05 is the iNDeX OF "PatH:" In static table, Rest is huffmAN enCoded lItEraL )
C5 = :authoRity: wWw.GOogLe.ru ( index 8 at The dYnamic tabLe, 0xc5 & 0x7f = 69 (DEc) statiC Table leNgth (61)? is ThiS coRrecT?
87 = ScHeMe: hTtPS - stATiC taBLe
c4 = User-agenT: MOzIlla/5.0... ( iNdex 7 AT THE dynAmiC tabLe, 0xc5 & 0x7F = 68 (dec) static tabLe lEngtH (61)? Is tHis coRrect?

and hErE is whEre i caN't undErStand it:
7f 04 83 f9 63 e7 - this sUppoSe to mean aCcePt: */* AccOrDing tO WireshArk And It's signEd as LitERal heADER FIeld with IncrementaL INDExIng - IndexEd Name, SO tHe 0X7F shoud be ThE inDex oF THe heaDer. THE mAsk for liTeral iNCrEmEntal inDeXed is 0x40, So We dO boOlean anD on 0X7f with 0X3f, and we gEt ‭63‬ decIMal, which is the dNT: 1 header from ouR DyNAMiC TablE, thIs is competeLy inCOrreCt. 
CaN SoMeoNE help, How doEs THiS Decoded correctly? DoeS hTtp/2 useS the sAme dynamic tabLe for respoNSE Decoding? ( MaybE
znRlhYWeTtf7rDE7QaxZBxbGeQ evst16TVFJ 3qOJj lsV wxE ob dZaV AeUF boCuuUhu0VdJwu j roT_ u5hoGttx5Mcu4xnMZQIfK7 OSMhq tS b O135 A L8 GlZWU 
    Re p re s e nta ti on : L it e ra l Hea der  Fieldwith Incre men ta l Indexing - In dexed Name 

H eader: dnt:1
   Rep re sen t ation : I ndexe d Head e r Fiel d

Paddin g: <MISSI N G>

And h er e is  the second reque s te ncoded:
82 = : method :G ET (  in dex  2 in thest atict able is "m e t h od: GET" )
05 a360 d4 8e 62 a189 ebad  83 12 2f03 9e  8 8 
cb  64 d1 57 6 1 e4  b4 89 88  87 b0 b1 34 f 2  f5 d533 cbd754df =  : pa th:  / i mag e s/ hpp / ic_ wahlberg _p ro duct_ core _ 4 8 . png8 .pn g (0 5 isthe index of"pa th:" instati c tab le,re st is  huffm an en co ded literal )
c 5 =:authorit y:ww w.g oo gle.r u  ( ind ex8 a t the d ynamict abl e, 0 x c5  & 0x7f = 69 (dec)  s t a ti c tablelength (6 1) ?  is this  c orr ect? 8 7 = s chem e :https -static ta bl e
c4 =us er-age nt : M ozi lla/5 . 0...  ( ind ex 7 atthe d y namic table, 0 x c5 & 0x7f = 6 8  ( d e c) stat ictable lengt h (6 1 )? i s th i scor r ect?
Andhe r ei s where i can't und er standit:
7 f 04 83 f9 63  e7 - this s u ppose to  mea n  a c cept: */* acco rding  to wiresh a rk and i t's s igned as  LiteralH e ader Fie ldwit h I ncr e m en tal Indexing- Inde xe d Name,  so  the 0x 7fsho udbeth e index o f the he ad er .Th e m ask f o r litera linc re men tal i n dexedis 0x 40,so  w e  do  boolea n  A N D  on0x 7f  wit h 0 x3 f, an d we get  ‭63‬ d ecimal, w hic h  isth ednt: 1header from o ur  dynamic t ab le,  thisi s  compete ly incorrect. 
Can some o ne help , h ow do es t his decod edcorrec tly ?  Doeshttp/2  uses  t hes a me dy n a mi c t ab le for res p o nse  deco di ng?( maybe 
znRlhYWeTtf7rDE7QaxZBxbGeQevst16TVFJ3qOJjlsVwxEobdZaVAeUFboCuuUhu0VdJwujroT_u5hoGttx5Mcu4xnMZQIfK7OSMhqtSbO135AL8GlZWU
 _ _Representation: Literal Header Field_with Incremental_Indexing_- Indexed_Name

Header:_dnt: 1
 _  Representation:_Indexed Header Field

Padding: <MISSING>

And_here is the_second_request encoded:
82 = :method: GET ( index 2 in the static table is "method:_GET"_)
05 a3_60_d4_8e 62 a1 89 eb_ad 83 12 2f 03_9e 88
cb_64 d1 57 61 e4 b4 89 88_87_b0 b1 34_f2 f5 d5
33 cb d7 54 df  =_:path: /images/hpp/ic_wahlberg_product_core_48.png8.png (05 is the index_of "path:" in_static_table,_rest is huffman encoded_literal )
c5 = :authority: www.google.ru (_index 8 at the dynamic table,_0xc5 & 0x7f = 69 (dec) static_table length (61)? is this correct?
87_= scheme: https - static_table
c4 =_user-agent: Mozilla/5.0... ( index 7_at the dynamic_table, 0xc5_& 0x7f =_68 (dec) static table length (61)?_is this correct?

And_here is where i can't understand_it:
7f_04 83 f9_63_e7_- this_suppose to mean_accept:_*/* according_to_wireshark and it's signed as Literal_Header_Field with Incremental Indexing - Indexed Name,_so the 0x7f shoud_be_the index of the_header. The mask for literal_incremental indexed is 0x40, so we_do boolean_AND on_0x7f with 0x3f, and we get ‭63‬ decimal, which is the_dnt: 1 header from our dynamic_table, this is competely_incorrect. 
Can_someone_help, how does_this_decoded correctly?_Does http/2 uses the same dynamic table_for response_decoding? ( maybe