W3C home > Mailing lists > Public > ietf-http-wg@w3.org > July to September 2015

Re: http/2 TRACE method

From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 9 Sep 2015 15:01:33 -0700
Message-ID: <CABkgnnVXTRvKN9=xYeYpnwiOfr+kODkcnD6K_xvTPBMH9Z1t8g@mail.gmail.com>
To: Francisco Moraes <francisco.moraes@gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>
TRACE echoes the request as message/http.  That doesn't need new
behaviour.  It does mean that the header fields will need to be
decoded so that they can be presented in that format (which is
basically the HTTP/1.1 form).

On 9 September 2015 at 14:07, Francisco Moraes
<francisco.moraes@gmail.com> wrote:
> Hi,
>
> I tried to find the answer for this question via Google but was not lucky.
> I've also checked the http/2 RFC but but found no answer as well.
>
> Wondering if you know what the behavior of the HTTP TRACE method should be
> with http/2. Should it just echo back the headers/response as decoded, as
> binary?
>
> It is not clear what a server response should be in this case or if it is
> even supported.
>
> Francisco
>
Received on Wednesday, 9 September 2015 22:02:02 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:46 UTC