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
Since Go http headers is store in a map and in Go 1 the runtime randomizes map iteration, so:
we need a way to let people define the order.
or at least Go set the default order by "good practice" as defined in RFC 2616, section 4.2:
The order in which header fields with differing field names are
received is not significant. However, it is "good practice" to send
general-header fields first, followed by request-header or response-
header fields, and ending with the entity-header fields.
The text was updated successfully, but these errors were encountered:
Yeah, what @mvdan said. But even that RFC text can be implemented without knowing the "original" order. I'd like to see evidence that anybody cares about the order before we even did that, though. I'd need a lot of evidence that order matters to somebody before adding new API around this.
Since Go http headers is store in a map and in Go 1 the runtime randomizes map iteration, so:
The text was updated successfully, but these errors were encountered: