Re:HTTPie is a command line HTTP client, a user-friendly cUR...
by diminoten on Friday June 13, 2014 @05:52PM
(#7891030)
Requests does use an ordered dictionary for handling headers.
[ Parent
| on HN ]
Re:HTTPie is a command line HTTP client, a user-friendly cUR...
by 0xhex on Friday June 13, 2014 @10:03PM
(#7891843)
Requests might but that's irrelevant. Requests is built on top of urllib3 which is built on top of httplib which does use a plain dict. Also the relevant RFC says order is irrelevant.
Re:HTTPie is a command line HTTP client, a user-friendly cUR...
by jacquesm on Saturday June 14, 2014 @04:59AM
(#7892399)
Debugging starts with having an accurate representation of what is going on.
Re:HTTPie is a command line HTTP client, a user-friendly cUR...
by oneeyedpigeon on Saturday June 14, 2014 @05:44AM
(#7892455)
Ok, so this tool is only for all the situations in which you don't care about header order.
Re:HTTPie is a command line HTTP client, a user-friendly cUR...
by zhng on Friday June 13, 2014 @08:19PM
(#7891544)
It should as order is important.
Re:HTTPie is a command line HTTP client, a user-friendly cUR...
by Franciscouzo on Friday June 13, 2014 @09:48PM
(#7891800)
www.ietf.org/rfc/rfc2616.txt
4.2 Message Headers
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.
Re:HTTPie is a command line HTTP client, a user-friendly cUR...
by throwaway5752 on Friday June 13, 2014 @10:26PM
(#7891895)
Yes, if you're implementing a client or server, you should not depend on the order of the headers. Completely separately, when I have a command line client for debugging, I want to see the request and response exactly as they were sent/received, respectively.
Re:HTTPie is a command line HTTP client, a user-friendly cUR...
by zhng on Friday June 27, 2014 @12:01PM
(#7954615)
> Instances of the same path and name will overwrite each other, with the latest instance taking precedence. Instances of the same path but different names will add additional mappings.
> When sending cookies to a server, all cookies with a more specific path mapping should be sent before cookies with less specific path mappings. For example, a cookie "name1=foo" with a path mapping of "/" should be sent after a cookie "name1=foo2" with a path mapping of "/bar" if they are both to be sent.