Fix nchan regex to prevent intercepting /sub/ in file paths #2494
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.
The regex pattern
~ /sub/(.*)$matched/sub/anywhere in the path, including file paths like/mnt/disk2/test/foo/sub/file.iso. This caused nginx to route these requests to the nchan subscriber endpoint instead of serving the files.Changed to
~ ^/sub/(.*)$to only match paths that start with/sub/, which is the correct behavior for the nchan websocket endpoint.Fixes #2493
Summary by CodeRabbit
✏️ Tip: You can customize this high-level summary in your review settings.