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
Hi @Sgitario, this behavior is expected. In fact, the build should fail if a similar @Route method is found. We should improve the validation logic - currently, it only fails if a method that return void does not declare any parameters. This logic is not valid since quarkus 1.7 where @Param, @Body and others non-RoutingContext params were added.
For the record - a @Route method must either (a) return non-void result or (b) end the response via one of the HttpServerResponse.end() methods.
Describe the bug
Having the next route:
When we call this route via CURL, it fails with
Read timed out
.Expected behavior
The service should return 204 No Content.
Actual behavior
The servide hangs to return anything.
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: