Characters outside of the URL spec can make Bitbucket throw uncaught 400 bad request exception

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

1. Access Bitbucket https://<BITBUCKET_BASE_URL>/projects/<PROJECT>/repos/<REPO>/browse/
2. Select a file;
3. 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.