stereobooster/react-snap

Create support scripts for `http2-push-manifest.json`

Open

#73 geöffnet am 27. Dez. 2017

Auf GitHub ansehen
 (2 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)JavaScript (4.982 Stars) (403 Forks)batch import
enhancementhelp wanted

Beschreibung

  • It is possible to create lua script for nginx, which will read http2-push-manifest.json and send appropriate headers.
  • It is possible to create ruby script for h2o, which will read http2-push-manifest.json and send appropriate headers.

continuation of https://github.com/stereobooster/react-snap/issues/3

Need to have demo server. Maybe Heroku or similar:

Heroku doesn't support HTTP2 so ¯\_(ツ)_/¯

Contributor Guide

Tech Stack
ruby
Domain
backendperformance
Issue Type
feature
SchwierigkeitGeschätzte Implementierungsschwierigkeit für neue Contributors, von 1 für sehr kleine Änderungen bis 5 für Expertenarbeit.
3
Geschätzte ZeitEin grober Zeitrahmen, um zu recherchieren, zu implementieren, zu testen und einen Pull Request vorzubereiten.
1-2 days
AktivitätsstatusWie verfügbar das Issue gerade wirkt: frisch, aktiv, stale, blockiert oder wartet auf Maintainer-Input.
stale
KlarheitWie klar das Issue die erwartete Änderung, Akzeptanzkriterien und den nächsten Schritt erklärt.
mostly clear
Voraussetzungen
HTTP/2 push basicsnginx or h2o configurationscripting in Lua or Ruby
EinsteigerfreundlichkeitEin Score von 1 bis 100, der schätzt, wie zugänglich dieses Issue für First-Time Contributors ist.
40
Research-Richtung
The issue requests creating Lua scripts for nginx and Ruby scripts for h2o that parse `http2 push manifest.json` and send appropriate HTTP/2 push headers. The repository is react snap, which uses JavaScript, but this task is about server side support. No existing pull requests or assignments exist, but the issue is old (2017) and stale. To proceed, one would need to understand HTTP/2 server push, the format of the manifest file, and how to write configuration extensions for nginx (using Lua) and h2o (using Ruby). Additionally, a demo server is required; many free hosting options that support HTTP/2 (e.g., from the list in the issue) should be evaluated. The deliverable is clear: two scripts and a working demo.