Server reliability, performance and security improvments#2061
Merged
Conversation
Deeper path validation, collision protection for backups, fixes missing config field crash, adds check for file size, improved security of filename allow regex
Adds a timeout to prevent ever lasting requests, surrounds JSON parse with try catch when header missing uses a 400 status code instead of 500 and fixes the error messaging for this
✅ Deploy Preview for dashy-dev ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This was referenced Apr 12, 2026
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Category
Bug fix + Improvments for robustness/reliability, security and performance of the server endpoints.
Overview
I went through all issues where users reported server crashes or restart loops. Each case which this could ever happen should now be gracefully handled, to prevent the Docker container from unexpectidly crashing.
Robustness
Security
Tests
Config changes
Nothing really, except there's a new
DANGEROUSLY_DISABLE_PROXY_RESTRICTIONSwhich if set will let you turn off all the newly implemented security safeguards (they're on by default).