stereobooster/react-snap

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

Open

#73 opened on Dec 27, 2017

View on GitHub
 (2 comments) (0 reactions) (0 assignees)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 ¯\_(ツ)_/¯

Contributor guide

Tech stack
ruby
Domain
backendperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
mostly clear
Prerequisites
HTTP/2 push basicsnginx or h2o configurationscripting in Lua or Ruby
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
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.