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
First step will be to collect a list of such headers that are only valid in certain http. versions, secure mode or other contexts... The Connection is already an example given here. The #67 (CH) issue also mentions already client hints only in secure mode. There might however be more, all can be listed here.... Question is if this needs to be a middleware or if perhaps we can just fo this as part of the UA web client?
This is already handled nicely by sanitize_client_req_header. For now keeping it there is okay, Depending if there are issues with it in future or it grows too much we can move it somewhere else, even though not sure where. For now it's ok as-is.
Client-Hints are for now out of scope, as the UA Emulation will set it already correctly based on what is desired, and any pre-defined CH's are up to the user to have done correctly.
E.g. strip out
Connection
header when a http version higher thenhttp/1.1
is requested.The text was updated successfully, but these errors were encountered: