-
Notifications
You must be signed in to change notification settings - Fork 138
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
<groovy/>
sets empty Response in the Response flow, when exc.getResponse() == null
#761
Comments
@t-burch Test and post how the wired response looks like (test with curl). I do not know if we should change something. Cause this might not the only Interceptor. Maybe we should check in the Transport if response==null and then provide an error message? |
In what circumstance does it set the 200 OK response, how can one reproduce that |
Remove setting 200 OK |
@rrayst I cannot reproduce the error and I can't find anything in GroovyInterceptor that could lead to this behaviour. |
No it returns:
|
(Use any interceptor producing an uncaught Exception after http://localhost:2000/ returns "200 OK". |
This leads to
producing weird
200 OK
responses in error cases.(This is due to:
api-gateway/core/src/main/java/com/predic8/membrane/core/interceptor/AbstractInterceptor.java
Line 136 in 3e20594
The text was updated successfully, but these errors were encountered: