Skip to content
This repository has been archived by the owner on May 17, 2023. It is now read-only.

fix forced ordering of transport header parameters? #15

Open
greywolf-colorado opened this issue Nov 6, 2012 · 0 comments
Open

fix forced ordering of transport header parameters? #15

greywolf-colorado opened this issue Nov 6, 2012 · 0 comments

Comments

@greywolf-colorado
Copy link
Contributor

I may be mistaken but I don't think the ordering of the parameters in the transport header is fixed (e.g. they could be in any order).
turboladen added a commit that referenced this issue Jul 2, 2013
@turboladen
Removed comments
499685e 
This is related to and should be fixed by the implementation of gh-15.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@greywolf-colorado