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
Queries that mistakenly include "smart quotes" result in an error in Elasticsearch that results in Rails sites throwing an error (because @res contains the 400 bad request. Example is "&q=text%3A%22future+the+only+authentic+and+perfect.%E2%80%9D" quotes are expected to be %22 which the API and ES can handle.
IN general, can 400 errors (and other ES errors) be handled better? Either with the contents of @res and/or how they are handled by Rails.
%22which the API and ES can handle.