Kurt Griffiths

P.S. It's interesting to note that HTTP/2 requires lowercased headers. I suspect it is an acknowledgement that allowing for case insensitivity leads to clients not always doing the right thing,...

I think we can mitigate much of the potential performance regression in doing this by not going through the mapping interface and just interacting with a standard library `dict` directly....

Given that HTTP/2 lowercases all headers anyway, and the protocol is becoming prevalent, is it worth the effort of addressing this after all?

(Scheduling for 2.1 since it requires stable 2.0 docs)

1.4 is on the home stretch, so let's take a look at this for 2.0

Note that extension relation types are REQUIRED to be absolute URIs.

Assigning this to 3.1 just so we don't forget to make a decision on it.

Adding to what @vytas7 said, we should also consider what patterns this will encourage/discourage and whether those are good things in the long run for the community.

Updated gist: https://gist.github.com/vytas7/cf49d061894bbff66e63b1dd9500e2cb I like the idea of starting a recipe section in the docs. Let's put this one in there as one of our first recipes. We should include...

(Please comment below re a design proposal if you are interested in taking this on, thanks!)