Open Bug 1407355 (earlyhints) Opened 6 years ago Updated 2 days ago

[meta] Implement 103 Early Hints

Categories

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

58 Branch
enhancement

Tracking

()

Tracking Status
firefox58 --- affected

People

(Reporter: dragana, Unassigned)

References

(Depends on 14 open bugs)

Details

(Keywords: meta, Whiteboard: [necko-triaged])

Attachments

(3 files)

Priority: -- → P2
Whiteboard: [necko-triaged]
I have patches for necko part of this bug. We should work on the dom part of the implementation in bug 1409290.
Depends on: 1409290
Change to httpd.js test server and a test for the 103 response.
The change to nsHttpTransaction.
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).
Priority: P2 → P3

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:

Depends on: 1394778

nodejs also supports it

The upcoming release of lighttpd 1.4.56 supports 103 Early Hints

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?

Flags: needinfo?(dd.mozilla)

(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 :) ).

Flags: needinfo?(dd.mozilla)
Keywords: meta
Depends on: 1740208
Summary: Implement 103 Early Hints → [meta] Implement 103 Early Hints
Depends on: 1740466
Depends on: 1740687
Depends on: 1740688
Depends on: 1740689
Depends on: 1740690
Depends on: 1740692

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

Depends on: 1741422
Depends on: 1741423
Depends on: 1743630
Depends on: 1744821
Depends on: 1744822
Assignee: dd.mozilla → nobody
Status: ASSIGNED → NEW
Depends on: 1746324
Depends on: 1744028
Depends on: 1743686
Depends on: 1753730
Depends on: 1761242
Depends on: 1761248
Depends on: 1761252
Depends on: 1761259
Depends on: 1763345
Depends on: 1765289
Depends on: 1765290
Depends on: 1760124
Depends on: 1771867
Depends on: 1773272
Depends on: 1774404
Depends on: 1780822
Alias: earlyhints
Depends on: 1781752
Depends on: 1783683
Depends on: 1783685
Depends on: 1783686
Depends on: 1783823
Depends on: 1783825
Depends on: 1783826
Depends on: 1783848
Depends on: 1784025

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

Depends on: 1790355
Severity: normal → S3
Depends on: 1795896
Depends on: 1798319
Depends on: 1797936
Depends on: 1798962
Depends on: 1798952
Depends on: 1799166
Depends on: 1799167
Depends on: 1799169
Depends on: 1800485
Depends on: 1801161
Depends on: 1801163
Depends on: 1801608
Depends on: 1802501
No longer depends on: 1744028
No longer depends on: 1761259
No longer depends on: 1765290
No longer depends on: 1783685
No longer depends on: 1746324
No longer depends on: 1795896
No longer depends on: 1798319
No longer depends on: 1798716
No longer depends on: 1800485
No longer depends on: 1801161
No longer depends on: 1801163
No longer depends on: 1760124
Depends on: 1803744
Depends on: 1803746
Depends on: 1803747
Depends on: 1803884
Depends on: 1804034
No longer depends on: 1761248
Depends on: 1806101
Depends on: 1806403
Depends on: 1808323
Depends on: 1808699
Depends on: 1809145
Depends on: 1809893
Depends on: 1809894
Depends on: 1810543
Depends on: 1810546
Depends on: 1805067
Depends on: 1811234
Depends on: 1812360
Depends on: 1813035
Depends on: 1813071
Depends on: 1813132
Depends on: 1813606
Depends on: 1813623
Depends on: 1813630
Depends on: 1815279
Depends on: 1815884
Depends on: 1815934
Depends on: 1816149
Depends on: 1820829
Depends on: 1822005
Depends on: 1836255
Depends on: 1836289
You need to log in before you can comment on or make changes to this bug.