You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was looking and this implementation and I have question regarding dynamic table specifically how reverse lookup works.
If I understand this correctly It first searches static table then goes to the dynamic table where it first checks if name + value are the same if that is not so it checks if only name is the same and if it is and it is not in the static table it returns this value.
But lets say for example that we have a dynamic table like this:
And you are encoding header"custom-name": "custom-value-2". In this case since header "custom-name" in not in the static table and because header "custom-name": "custom-value-1" is on the top of dynamic table the encoder will take index 1 and do literal encoding for value instead of using direct match of both name and value at index 3.
Is my understanding of this correct? And if so is this a bug?
The text was updated successfully, but these errors were encountered:
I was looking and this implementation and I have question regarding dynamic table specifically how reverse lookup works.
If I understand this correctly It first searches static table then goes to the dynamic table where it first checks if name + value are the same if that is not so it checks if only name is the same and if it is and it is not in the static table it returns this value.
But lets say for example that we have a dynamic table like this:
And you are encoding header
"custom-name": "custom-value-2"
. In this case since header"custom-name"
in not in the static table and because header"custom-name": "custom-value-1"
is on the top of dynamic table the encoder will take index 1 and do literal encoding for value instead of using direct match of both name and value at index 3.Is my understanding of this correct? And if so is this a bug?
The text was updated successfully, but these errors were encountered: