Open riyazuddinsyed opened 4 days ago
It was observed that searching using 3 invalid characters (like "$$$") gets passed to Business Search and does not result in an HTTP 500.
It could be argued that the UI should filter out spaces, but it doesn't filter out other invalid characters. Also, the API should protect itself from invalid search parameters instead of crashing with a SOLR error.
@mstanton1 If search function isn't managed by BTR Team, please re-assign. Thanks.
@severinbeauvais the search API is managed by the BTR team. A key question is whether we should be stripping any characters. An organizational goal is to move towards support for indigenous and French characters. With the BTR filing we've allowed all ascii characters for significant individuals which may be a way to proceed with companies as well. My understanding of the historical reason we didn't allow dollar signs in names was because there was a mainframe limitation. When search work is picked up again next PI we can look at this further.
So there's a discrepancy: the Search API does not crash if the UI requests a search for "$$$", but it does crash if the UI requests a search for " " (3 spaces).
Thanks for the clarity. I will connect with Kial next PI on this one, unless we find a number of ops tickets coming in as a result which would warrant finding another resource to tackle this sooner.
Describe the bug in the current situation When a user enters extra spaces in the business lookup search, the Business Search API fails and returns a 500 Internal Server Error. This issue does not occur when special characters or other inputs are entered, suggesting that the presence of extra spaces is causing an unexpected failure in the backend.
Steps to reproduce the behavior:
Screenshots/ Visual Reference/ Source