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 have tried using the CRITICAL-CH header(#123) to request a client retry when client hints were missing due to out-of-date preferences. However, I understand that this approach may not be suitable in certain cases, as it requires the load to restart in order to return the now-cached client hints.
In light of this, I am interested in finding an alternative solution such as the ACCEPT_CH frame, which may allow me to avoid the retry in most cases by delivering the client hints as part of connection setup.
Therefore, I am specifically looking for examples or documentation on how to implement the ACCEPT_CH frame on a load balancer, rather than the CRITICAL-CH header. Could someone provide an example or point me to some documentation on how to implement the ACCEPT_CH frame on a load balancer? I would greatly appreciate any guidance on this topic.
Thank you!
The text was updated successfully, but these errors were encountered:
I have tried using the CRITICAL-CH header(#123) to request a client retry when client hints were missing due to out-of-date preferences. However, I understand that this approach may not be suitable in certain cases, as it requires the load to restart in order to return the now-cached client hints.
In light of this, I am interested in finding an alternative solution such as the ACCEPT_CH frame, which may allow me to avoid the retry in most cases by delivering the client hints as part of connection setup.
Therefore, I am specifically looking for examples or documentation on how to implement the ACCEPT_CH frame on a load balancer, rather than the CRITICAL-CH header. Could someone provide an example or point me to some documentation on how to implement the ACCEPT_CH frame on a load balancer? I would greatly appreciate any guidance on this topic.
Thank you!
The text was updated successfully, but these errors were encountered: