fix(prerenderer): HEAD requests cause double requests #594
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
HEAD /nojs/address/... took 2530ms and returned 878259 bytesThis proves HEAD requests are generating the full HTML body (878KB) and taking 2.5 seconds - the same expensive operation as GET requests.
The code confirms this: in server.js, every request (HEAD or GET) calls render(), which runs the full Cycle.js app to generate HTML. Express handles HEAD by not sending the body, but the work is still done.
The proxy uses HEAD requests to check if pages exist (200 vs 404/500), not to get content-length. The prerender determines status codes without needing the full HTML body.