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
Headers according to HTTP 1.1 don't have to be unique and can be repeated. fetch.Error.Headers filters them out and takes the last one. fetch.Response handles it with DuplicateHeaders field and Headers() method. fetch.Error should handle it in the same, but it would break backward compatibility.
The text was updated successfully, but these errors were encountered:
Actually, I don't like Headers() method. It's nicer if it's a field. If I'm breaking backward compatibility then, I should go for the nice one everywhere.
Headers according to HTTP 1.1 don't have to be unique and can be repeated.
fetch.Error.Headers
filters them out and takes the last one.fetch.Response
handles it withDuplicateHeaders
field and Headers() method.fetch.Error
should handle it in the same, but it would break backward compatibility.The text was updated successfully, but these errors were encountered: