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
For feature detection some of us have been discussing that we could add Accept: application/signed-exchanges headers. However given that SXG can have any resources it looks the UAs that support SXG always need to attach / append SXG type even when anything can be accepted, so it could look something like Accept: application/signed-exchange;q=0.9,*/*;q=0.8 for default, non-specific subresource requests. Would it be just or if we want to think about alternative feature detection mechanism (e.g. specific headers etc)?
The text was updated successfully, but these errors were encountered:
For feature detection some of us have been discussing that we could add Accept: application/signed-exchanges headers. However given that SXG can have any resources it looks the UAs that support SXG always need to attach / append SXG type even when anything can be accepted, so it could look something like
Accept: application/signed-exchange;q=0.9,*/*;q=0.8
for default, non-specific subresource requests. Would it be just or if we want to think about alternative feature detection mechanism (e.g. specific headers etc)?The text was updated successfully, but these errors were encountered: