Skip to content

fix: make non-existent asset paths return a 404 #14472

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Aug 29, 2024
Merged

Conversation

code-asher
Copy link
Member

@code-asher code-asher commented Aug 28, 2024

Before, if a file was not found we would serve the app. I do not think we were relying on falling back to the app for /assets so should be safe to just return a 404 instead.

Fixes #14409

Before, if a file was not found we would serve the app.
@code-asher code-asher marked this pull request as ready for review August 28, 2024 18:14
@code-asher
Copy link
Member Author

code-asher commented Aug 28, 2024

@BrunoQuaresma we are not relying on /assets or /assets/* serving the app anywhere, right? Just want to make sure I am not breaking something in the frontend by handling missing assets in the backend

@code-asher code-asher requested a review from Emyrk August 29, 2024 17:19
@code-asher
Copy link
Member Author

Just realized @BrunoQuaresma is out for a bit, so going to request someone else

Copy link
Member

@Emyrk Emyrk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch 👍

@code-asher code-asher merged commit cd38e29 into main Aug 29, 2024
27 checks passed
@code-asher code-asher deleted the asher/asset-404 branch August 29, 2024 21:52
@github-actions github-actions bot locked and limited conversation to collaborators Aug 29, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

/assets/* always returns 200 OK
2 participants