freeCodeCamp/disable-client-side-caching-with-helmet.nocache.english.md at 6b3c61c73757d6ffe2ea332cbc44dad7948d1175

Files

Kristofer Koishigawa 6b3c61c737 feat: update backend project links (#39314 )

* feat: update backend project links

Replace solution and remix Glitch links with equivalent Repl.it links in backend projects/challenges and intro pages.

* fix: link and Repl.it casing

* fix: update mention of glitch in testing challenge

* Apply suggestions from code review

Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>

Co-authored-by: Mrugesh Mohapatra <1884376+raisedadead@users.noreply.github.com>
Co-authored-by: Oliver Eyton-Williams <ojeytonwilliams@gmail.com>

2020-08-17 14:38:16 -07:00

1.5 KiB

Raw Blame History

id, title, challengeType, isHidden, forumTopicId

id	title	challengeType	isHidden	forumTopicId
587d8249367417b2b2512c3e	Disable Client-Side Caching with helmet.noCache()	2	false	301576

Description

As a reminder, this project is being built upon the following starter project on Repl.it, or cloned from GitHub. If you are releasing an update for your website, and you want the users to always download the newer version, you can (try to) disable caching on client’s browser. It can be useful in development too. Caching has performance benefits, which you will lose, so only use this option when there is a real need.

Instructions

Tests

tests:
  - text: helmet.noCache() middleware should be mounted correctly
    testString: getUserInput => $.get(getUserInput('url') + '/_api/app-info').then(data => { assert.include(data.appStack, 'nocache'); assert.equal(data.headers['cache-control'], 'no-store, no-cache, must-revalidate, proxy-revalidate'); }, xhr => { throw new Error(xhr.responseText); })

Challenge Seed

Solution

/**
  Backend challenges don't need solutions, 
  because they would need to be tested against a full working project. 
  Please check our contributing guidelines to learn more.
*/

1.5 KiB Raw Blame History Unescape Escape