Open af-jul opened 1 year ago
@af-jul just wondering: Does this bug only happen with the 401 status code?
@NghiaTranUIT that's actually hard to test. It seems like the issue only occurs if the server already responds with this status code and not if I modify the code when the response hit the breakpoint. I was at least able to get the same issue on 404 (that's easy to get from the server) but I'm not sure about other status codes.
Description
I have the following in my App:
If I don't specify any breakpoints in Proxyman everything works well, but as soon as I enable response breakpoints and deliver the 401 to my App, my retry call that uses the same connection as the original request fails with a
java.net.ProtocolException: Unexpected status line: 0
while establishing the connection. So it appears that this connection has silently be closed.Steps to Reproduce
Connection: close
header in the 401 response after it hit the breakpoint, seems to work but is not my desired solutionCurrent Behavior
Proxyman seems to silently close the connection when receiving a 401 response from the server and delivering it back to my App. Further requests on the same connection fail, with such a breakpoint in between, while it is working when I disable the breakpoints.
Expected Behavior
The connection should be kept open / mirror the server state.
Environment