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
But by now we have to specify all the headers not just few we want to focus on.
It's because isRequestHeadersMatching finally uses deepEqual to find appropriate handler.
Is it intentional for any reason? If no, I'd like to send a patch.
PS Also see no docs on headers filtering at main page. Is it also intentional for any reason(like API has not stabilized yet and still may change or kind of that)? If no, I'd like to help on that too.
The text was updated successfully, but these errors were encountered:
skyboyer
changed the title
headers filtering is too
headers filtering is too strict
Oct 11, 2019
Headers validation has been implemented in #70 to make such a thing:
But by now we have to specify all the headers not just few we want to focus on.
It's because
isRequestHeadersMatching
finally usesdeepEqual
to find appropriate handler.Is it intentional for any reason? If no, I'd like to send a patch.
PS Also see no docs on
headers
filtering at main page. Is it also intentional for any reason(like API has not stabilized yet and still may change or kind of that)? If no, I'd like to help on that too.The text was updated successfully, but these errors were encountered: