User Inputs for Searching Can Results in Query Errors

[joncameron]

Description

There are two main areas where we see 500 errors in the application from bad URIs:

• Item view pages can have lots of junk
• Catalog search

Is extra handling an option so users get an "not found" page rather than a 500?

Users get a "Sorry, I don't understand your search" for some bad URI requests but not others. The honeybadger error below is an example of this case.

Done Looks Like

• [ ] Adding more error handling application-wide for invalid requests errors - return the "can't search" user notification instead of returning a 500 page
• [ ] Add flash message with restricted or invalid characters to display to user when error is caught
• [ ] Test searches with special characters (see #5971) to confirm error handling

[cjcolvar]

See https://app.honeybadger.io/projects/54117/faults/104411152/01J6AH2VTFA9B23ZB9P0W5229A#notice-summary for an example of a search that doesn't get the user input sanitized enough and ends up breaking the solr query.

[joncameron]

These cases could also be caught in the ApplicationController so that users get redirected to the home page across the board when making bad requests.