Closed tanandre closed 1 month ago
@tanandre I agree that is a bug. Two things though:
I think you are on the 1.x branch of Zuul, which is not supported anymore. I don't think we can dedicate the time to fix this. If you want to send a PR, I'd be happy to review it though.
I don't see from the second stack trace which filter is trying to access the request.
@carl-mastrangelo thanks I'll try to upgrade to version2.x first and see if that fixes our issue.
This issue is stale because it has been open 60 days with no activity. Remove stale label or comment or this will be closed in 7 days.
This issue was closed because it has been stalled for 7 days with no activity.
I'm proxying a call from the zuul proxy to my local tomcat using SSL with mismatching certificates (to test handling of an SSL error). This results in the 2 stacktraces below. The first stackTrace is the SSL error. The second stackTrace is where FilterProcessor is throwing an exception because it is trying to read from the request stream that is already closed which I believe is a bug. This is preventing the error from being handled in my error handler.
Stacktrace 1:
Stacktrace 2: