-
Notifications
You must be signed in to change notification settings - Fork 378
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How can the response of GraphQL inner http status codes be examined? #79
Comments
Hi @bigman73 Currently success/fail logic is simple. If Ddosify receives the response, that is a successful request/response cycle. If somehow a request couldn't send or response couldn't received (like timeout) then it is a failed cycle. Ddosify provides HTTP response codes to let the developer parse it and create their own assertion logic. Using stdout-json as the output type makes this process simpler. We'll implement a custom assertion logic, so you can easily create your own success/fail criteria. Like, if the response body contains |
Hi @kursataktas A custom regular expression seems like a very good solution. |
GraphQL operations that fail still return a 200 HTTP status code even if the inner resolvers fail
How can ddosify be used with GraphQL operations?
I'd like to see ddosify fail when inner GraphQL resolvers fail. Right now there's a success for failed executions since the GraphQL response is 200 on the external response.
The text was updated successfully, but these errors were encountered: