stereobooster/react-snap

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

Open

#73 ouverte le 27 déc. 2017

Voir sur GitHub
 (2 commentaires) (0 réactions) (0 assignés)JavaScript (4 982 stars) (403 forks)batch import
enhancementhelp wanted

Description

  • 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 ¯\_(ツ)_/¯

Guide contributeur

Stack technique
ruby
Domaine
backendperformance
Type d'issue
feature
DifficultéDifficulté estimée pour un nouveau contributeur, de 1 pour un très petit changement à 5 pour un travail expert.
3
Temps estiméFourchette de temps approximative pour investiguer, implémenter, tester et préparer une pull request.
1-2 days
Statut d'activitéDisponibilité apparente de l'issue : fraîche, active, ancienne, bloquée ou en attente d'un mainteneur.
stale
ClartéClarté avec laquelle l'issue explique le changement attendu, les critères d'acceptation et la prochaine étape.
mostly clear
Prérequis
HTTP/2 push basicsnginx or h2o configurationscripting in Lua or Ruby
Accessibilité débutantScore de 1 à 100 estimant l'accessibilité de cette issue pour un premier contributeur.
40
Direction de recherche
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.