Description
Issue Summary
When adding encoded character to a Bitbucket URL the application throws an throws uncaught 400 bad request exception back to the user instead of treating the error in an error page, such as it does when a 404 not found error happens.
Steps to Reproduce
- Access Bitbucket https://<BITBUCKET_BASE_URL>/projects/<PROJECT>/repos/<REPO>/browse/
- Select a file;
- add the following to the end of the URL
?\
Expected Results
Bitbucket should treat the error and shows a 400 - bad request page, similar to the 404 error page.
Actual Results
Bitbucket does not treat the error and shows the error that is is thrown by the webserver.
Workaround
No workaround available at this moment.
Attachments
Issue Links
- is duplicated by
-
BSERV-12865 Viewing a file in Source View with backslashes throws 400
- Closed
- causes
-
SSP-48651 Loading...