Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

Cloudflare caches pre-rendered response

Open
#194 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
18/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
express, javascript, node.js
Domain
backend, cloud

Research direction

Start by reviewing the Cloudflare CDN behavior and how the prerender-node middleware handles the cache-control:no-cache header. Reproduce the first and second responses described in the issue, then document or verify a configuration that prevents the pre-rendered response from being cached; no source file or test is named.

Written by the indexing model from the issue text.

Description

We are using Cloudflare as CDN
when we use pre-rendered.io with headers "cache-control:no-cache"
, then first response comes fine, but the second response from pre-rendered get cached in Cloudflare
I don't want to cache the pre-rendered.io response to Cloudflare
can somebody help me how do I configure prerender.io with Cloudflare?

Dominant language
JavaScript
Stars
921
Forks
185
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from prerender/prerender-node

All issues in prerender/prerender-node

Similar issues

More JavaScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.