1407355 - (earlyhints) [meta] Implement 103 Early Hints

Status: NEW

(Core :: Networking: HTTP, enhancement, P3)

Description

[Dragana Damjanovic [:dragana]]

https://github.com/httpwg/http-extensions/blob/master/draft-ietf-httpbis-early-hints.md

Comment 1

[Dragana Damjanovic [:dragana]]

I have patches for necko part of this bug. We should work on the dom part of the implementation in bug 1409290.

Comment 2

[Dragana Damjanovic [:dragana]]

Attachment: bug_1407355_test_v1.patch

Change to httpd.js test server and a test for the 103 response.

Comment 3

[Dragana Damjanovic [:dragana]]

Attachment: bug_1407355_v1.patch

The change to nsHttpTransaction.

Comment 4

[Dragana Damjanovic [:dragana]]

Attachment: bug_1407355_propagate_early_hint_part1_v1.patch

Propagate early hint response from parent to the child.
I have implemented a new interface nsIEarlyHintObserver instead of extended nsIRequestObserver.

It is possible to extend nsIRequestObserver as well, this only depends on how many observer we will really have and that depends on how we implement bug 1409290. Maybe we will need to propagate early hint responses through the listener chain(in that case we should extend the nsIRequestObserver interface).

Comment 5

[OptionallyNamed]

Make my page loading time faster. I am tired of slow loading time. Be faster than Chrome and implement it. Stop being the slowest browser.

Comment 6

[Renaud Chaput]

Any news on this?

I expect that website owners will only start to use early hints once a major browser supports it, but server-side support has been added in several servers/frameworks, for example:

• Apache HTTPD: https://httpd.apache.org/docs/2.4/howto/http2.html#earlyhints
• Puma & Rails (Ruby): https://eileencodes.com/posts/http2-early-hints/

Comment 7

[dalimian]

nodejs also supports it

Comment 8

[gstrauss]

The upcoming release of lighttpd 1.4.56 supports 103 Early Hints

Comment 9

[Benjamin De Kosnik [:bdekoz]]

Some movement here on the chrome side, intent to prototype:
https://groups.google.com/a/chromium.org/g/blink-dev/c/DAgWIczGtG0/m/gSXvjYn-AwAJ

From this design:
https://docs.google.com/document/d/1gCh_CnfrJq_VL7aGoq6skc7sn4yn5pKsM0gkHe5B9go/edit#heading=h.yh1rfx1p5ocs

Dragana, not quite sure if the proposed use of 103 reponse for a chrome trial is a great idea. Any thoughts?

Comment 10

[Dragana Damjanovic [:dragana]]

(In reply to Benjamin De Kosnik [:bdekoz] from comment #9)

Some movement here on the chrome side, intent to prototype:
https://groups.google.com/a/chromium.org/g/blink-dev/c/DAgWIczGtG0/m/gSXvjYn-AwAJ

From this design:
https://docs.google.com/document/d/1gCh_CnfrJq_VL7aGoq6skc7sn4yn5pKsM0gkHe5B9go/edit#heading=h.yh1rfx1p5ocs

Dragana, not quite sure if the proposed use of 103 reponse for a chrome trial is a great idea. Any thoughts?

This is on my radar already. The document shows interesting possible performance improvement from the telemetry they have collected (it sounds also a bit high). There is not a good spec for this feature, e.g. integration with fetch spec is missing. In one of the docs they proposed 2 possible implementation, but I would prefer to have some spec or at lease a draft that we can discuss. Anne had similar comment.

I was thinking about adding telemetry to estimate possible performance improvement in Firefox (if you are interested to help :) ).

Comment 11

[L]

Is this picking up steam now here due to Cloudflare enabling beta Early Hints on accounts?

Comment 12

[gfowler1]

This is live in Cloudflare and out of beta, I just toggled it on for my website.