Add config option to disable cache headers #2425
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
✅ Deploy Preview for electric-next ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
for embedded electric, in dev mode we don't want the browser to cache responses because it causes problems with restarts/migrations etc, so add a flag to just turn them off. also includes allowing configuration of the stack_ready_timeout and a higher default for that (was 100ms which is a bit harsh)
magnetised
force-pushed
the
magnetised/disable-api-cache-headers
branch
from
eb72e0d to
389e12a
Compare
icehaunter
approved these changes
Mar 7, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
for embedded electric, in dev mode we don't want the browser to cache responses because it causes problems with restarts/migrations etc, so add a flag to just turn them off.
also includes allowing configuration of the stack_ready_timeout and a higher default for that (was 100ms which is a bit harsh)