browserify/wzrd.in

Add cache headers (etag, last-modified, max-age, etc) + 304 Not Modified

Open

#62 opened on Jan 24, 2014

View on GitHub
 (7 comments) (1 reaction) (0 assignees)JavaScript (630 stars) (98 forks)batch import
help wantedof-concern

Description

I've noticed that because browserify doesn't include any of these, Chrome 32 will ALWAYS re-download the wzrd.in files on each new page load. This is really slow and frustrating.

Contributor guide

Tech stack
nodejsexpress
Domain
backendapiperformance
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
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.
clear
Prerequisites
HTTP cachingNode.jsExpress
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65
Research direction
Investigate the main route handler (likely server.js or route.js) that serves the bundled JavaScript. Add logic to compute ETag (e.g., MD5 hash of response body) and set it along with Last Modified and Cache Control headers. Handle incoming If None Match or If Modified Since headers to return a 304 Not Modified status with empty body. Test with Chrome dev tools to confirm caching behavior.