Consider moving less common headers into another crate

[reem]

These headers come with undesirable properties, like additional dependencies, which might not be ideal for the core hyper repo. If we somehow isolated them and hyper itself, I think it would lead to more stability. This might not be a concern since 1.0 is soon and things should hopefully chill out.

[pyfisch]

I propose to keep them in hyper but to make them opt-in using cargo features.

There could be the following groups of opt-in header fields:

• RFC7231: Semantics and Content#Content Negotiation; negotiation
• RFC7232: Conditional Requests; conditional
• RFC7233: Range Requests; range
• RFC7234: Caching; caching
• RFC7235: Authentication; authentication
• RFC6265: State Management Mechanism; cookie
• CORS; cors

The headers folder can be reorganised to represent the optional header fields. We can discuss if any of these groups should be included in the default compilation. There are still some non-essential header fields that remain in default like Server or Referer, maybe we can also make them optional.

[seanmonstar]

I don't think this is much of a problem.

On Sun, Mar 1, 2015, 5:36 AM Pyfisch notifications@github.com wrote:

I propose to keep them in hyper but to make them opt-in using cargo
features.

There could be the following groups of opt-in header fields:

• [RFC7231: Semantics and Content#Content Negotiation]; negotiation
• RFC7232: Conditional Requests http://tools.ietf.org/html/rfc7232;
  conditionals
• RFC7233: Range Requests http://tools.ietf.org/html/rfc7233; ranges
• RFC7234: Caching http://tools.ietf.org/html/rfc7234; caching
• RFC7235: Authentication http://tools.ietf.org/html/rfc7235;
  authentication
• RFC6265: State Management Mechanism
  http://tools.ietf.org/html/rfc6265; cookies
• CORS http://www.w3.org/TR/cors/; cors

The headers folder can be reorganised to represent the optional header
fields. We can discuss if any of these groups should be included in the
default compilation. There are still some non-essential header fields that
remain in default like Server or Referer, maybe we can also make them
optional.

—
Reply to this email directly or view it on GitHub
#317 (comment).

[soc]

I just experienced this. For simple use-cases like "download this file" the dependencies of cookies are really unfortunate.

Cookies depends on various unicode libraries, and unicode stuff is quite large due to the need of a lot of code and/or data to handle all the rules.

[seanmonstar]

@soc The only dependency in cookie that would bring in unicode stuff is url, and that is already a dependency of hyper.

---

If there are specific headers that don't belong in hyper because practically no one uses them, I'd approve their removal. However, I'm going to close this issue because of its broadness.