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
@darrelmiller This was my first thought upon reading the spec. However, I think it might be useful in RateLimit-Policy if the server knows up-front what the partition keys are and how different policies might apply to each. Admittedly, this would be communicating a fairly complex policy to the client, and it's exhaustively informative. Still, I think there's value.
Although the draft currently suggests it is supported https://datatracker.ietf.org/doc/html/draft-ietf-httpapi-ratelimit-headers-08#section-3.1.4 upon further reflection I do not believe it is useful. It is also harmful in that it would negatively effect the benefits of HPACK compression.
I think it is only useful on the
RateLimit
fieldThe text was updated successfully, but these errors were encountered: