You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
so in the search bar, or in the Search terms: of Detailed Search if you include any of the following characters in your search
" or { or }
you get a error
in this example i search for " and i am redirected to the url: http://127.0.0.1/search?query=%22&category=any&type=all&order_by=newest
"{"error":{"root_cause":[{"type":"query_parsing_exception","reason":"Failed to parse query [*\"*]","index":"marketplace","line":1,"col":58}],"type":"search_phase_execution_exception","reason":"all shards failed","phase":"query","grouped":true,"failed_shards":[{"shard":0,"index":"marketplace","node":"dELvXojzTsWKXtVhGARHrA","reason":{"type":"query_parsing_exception","reason":"Failed to parse query [*\"*]","index":"marketplace","line":1,"col":58,"caused_by":{"type":"parse_exception","reason":"Cannot parse '*\"*': Lexical error at line 1, column 4. Encountered: <EOF> after : \"\\\"*\"","caused_by":{"type":"token_mgr_error","reason":"Lexical error at line 1, column 4. Encountered: <EOF>
then my Whole .env file is displayed. it seems this is done by the Whoops PrettyPageHandler.php
in the code i found that it dumps the following on the page
so in the search bar, or in the Search terms: of Detailed Search if you include any of the following characters in your search
" or { or }
you get a error
in this example i search for " and i am redirected to the url:
http://127.0.0.1/search?query=%22&category=any&type=all&order_by=newest
with the following
/var/www/eckmar/vendor/elasticsearch/elasticsearch/src/Elasticsearch/Connections/Connection.php
Arguments
then my Whole .env file is displayed. it seems this is done by the Whoops PrettyPageHandler.php
in the code i found that it dumps the following on the page
i think its an issue with sanitizing but im not sure? can anyone shed some light please.
The text was updated successfully, but these errors were encountered: