-
Notifications
You must be signed in to change notification settings - Fork 613
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Respond with HTTP 404 if bundle entry point cannot be resolved
Summary: Changelog: **[Fix]** Respond with HTTP 404 when a bundle entry point cannot be resolved. Currently, Metro uses HTTP code 500 (Internal Server Error) for all errors. In the case of "bundle not found" errors, it can be useful to respond with 404 (Not Found) instead. This seemingly was Metro's behaviour at one point (D9772264) but has since regressed. Reviewed By: huntie Differential Revision: D51856058 fbshipit-source-id: 63ea7a7cbab5b0347def962867dcc720ac84946b
- Loading branch information
1 parent
2c718eb
commit cbfb96d
Showing
2 changed files
with
36 additions
and
5 deletions.
There are no files selected for viewing
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
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