Do we need the :method header?

[jyasskin]

#60 (comment) points out that we might not want to store the :method header in requests. We only know of uses of GET requests, and having the ability to code other methods might cause bugs.

[bmeck]

I vote it is uneeded.

[ibnesayeed]

From an archival perspective it might be important to keep it. Also, apart from GET there are other methods that might be useful, such as, HEAD and OPTIONS or any other methods that do not change the state of the resource.

[jyasskin]

We'd already restricted the method to be safe and [cacheable] (https://tools.ietf.org/html/rfc7231#section-4.2.3). Since the creation of HTTP, only GET and HEAD have met those requirements, and HEAD responses can be synthesized from a stored GET response. So #360 is dropping the :method field (since it would be the only remaining field in the request map).

[jyasskin]

#360 is merged. If a particular archival use case comes up, we can reopen the question.

[ibnesayeed]

@jyasskin do we have a way to support OPTIONS request without this header? If not, then how will the CORS requests work that need pre-flight requests?