Re: Working Group Last Call: draft-ietf-httpbis-early-hints-02

On 2017-05-26 00:00, Kazuho Oku wrote:
> Hi Julian,
> 
> Thank you very much for the suggestions. My comments in-line.
> 
> 2017-05-19 23:06 GMT+09:00 Julian Reschke <julian.reschke@gmx.de>:
>> Here's my feedback (and yes, as stated elsewhere, there should be at least
>> one example in the spec):
>>
>>
>> 1.  Introduction
>>
>>     The "preload" ([Preload]) link relation can be used to convey such
>>     links in the Link header field of an HTTP response.  However, it is
>>     not always possible for an origin server to generate a response
>>     header block immediately after receiving a request.  For example, the
>>
>> Maybe s/generate a response header block/generate a final response/?
> 
> How about https://github.com/httpwg/http-extensions/pull/353?

Looks good to me...

>>     HTTP/2 ([RFC7540]) server push can be used as a solution to this
>>     issue, but has its own limitations.  The responses that can be pushed
>>     using HTTP/2 are limited to those belonging to the same origin.
>>     Also, it is impossible to send only the links using server push.
>>
>> That's not clear to me. We could HTTP/2-push a HEAD response with link
>> header fields, no? Or a GET response which has links in the payload...
> 
> Does changing the last sentence of the quote to "Also, it does not
> define a way to push the links only." sound reasonable to you?

Yes.

> The paragraph lists what cannot be done under the current state of
> HTTP/2, namely: pushing a resource belonging to a different origin,
> push links only, avoid resending an already cached response.
> 
> All the other suggestions seemed to me that nobody would object, hence
> went directly into master in
> https://github.com/httpwg/http-extensions/commit/339ac0fff9524f04e80dfc48db4f3ba3eb8963f6.
> 
> Thank you very much for your help.
> ...

You're welcome :-)

Best regards, Julian

Received on Friday, 26 May 2017 07:27:54 UTC