[TASK] Handle 414 URI Too Long SolrCommunicationException with error message

Open christophlehmann opened this issue 1 year ago • 1 comments

What should be done in the scope of this task?

Anyone can post too long search inputs. These results in an alert with a big stackstrace.

Wed, 10 Apr 2024 21:40:47 +0200 [ALERT] request="223d9b74bf0b5" component="TYPO3.CMS.Frontend.ContentObject.Exception.ProductionExceptionHandler": Oops, an error occurred! ... SolrCommunicationException: Invalid query. Solr returned an error: 414 URI Too Long, in file /.../vendor/apache-solr-for-typo3/solr/Classes/System/Solr/Service/SolrReadService.php:98 - {"exception":"ApacheSolrForTypo3\\Solr\\System\\Solr\\SolrCommunicationException: Invalid query. Solr returned an error: 414 URI Too Long in /.../vendor/apache-solr-for-typo3/solr/Classes/System/Solr/Service/SolrReadService.php:98

Errors through invalid user input should be handled more gracefully - showing an error message or similar.

Apr 10 '24 20:04 christophlehmann

Thanks @christophlehmann for the issue :-)

I stumble over the same issue searching just for "*". On customer instances with the same configuration, database and docker image, this query works as expected.

Jul 17 '25 14:07 mschwemer