Despite the work in #439 , we see InvocationInputParseException errors caused by client disconnects that are logged as ERROR by AbstractGraphQLHttpServlet.
We can provide our own GraphQLHttpServlet that stops this, but it seems like there should be a way to intercept and silence these?
Despite the work in #439 , we see
InvocationInputParseExceptionerrors caused by client disconnects that are logged as ERROR byAbstractGraphQLHttpServlet.We can provide our own
GraphQLHttpServletthat stops this, but it seems like there should be a way to intercept and silence these?