Allow binding to HTTP headers

[brettsam]

Can we expand binding to headers as well as the body and query string? Example -- someone has a third party library that sends requests with an id in the header. It'd be nice if they can bind to that directly -- http://stackoverflow.com/questions/39036629/for-azure-documentdb-input-binding-is-there-a-way-to-get-the-document-id-from-t

[mathewc]

Perhaps. As part of merging in the http routing work, we'll also be expanding binding data to include route parameters, so we'll be doing more work in this area :)

[mathewc]

Closing this, since I don't think we should allow binding to headers. If we get customer asks for this, we can revisit.

[brettsam]

Can you explain why we shouldn't do this? This issue was created due to a customer ask, which seemed like a pretty reasonable scenario, so it'd be good to capture the reasons to close it.

[mathewc]

Sorry, I missed the SO link above. Unlike the route and query parameters, the headers collection can contain a lot of superfluous stuff that I don't think want to dump into the binding data bag.

I'll open this back up and assign back to triage so we can discuss further.