-
Notifications
You must be signed in to change notification settings - Fork 174
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
A proxied request hangs if a request to the original site emits an error #1961
Comments
I think that is what I am dealing with in this ticket |
any updates about the problem? |
No updates yet. You will be automatically notified once we make progress. |
This thread has been automatically locked since it is closed and there has not been any recent activity. Please open a new issue for related bugs or feature requests. We recommend you ask TestCafe API, usage and configuration inquiries on StackOverflow. |
I don't know if this can be reproduced in production, but likely it can.
Take a looks at the error handlers of the DestinationRequest's
req
object:_onError at src/request-pipeline/destination-request/index.ts
error at src/request-pipeline/utils.ts
If an error can't be handled by any brach in the
_onError
handler, it will be handled by the genericerror
handler, that just sets thectx.hasDestReqErr
and doesn't set thectx.goToNextStage
flag. After that the first flag is not handled by any code because without the second request pipeline silently terminates here just after the request is resolved.How to reproduce:
(optional) Add logging statements or breakpoints:
test/playground/server.js:24
src/request-pipeline/index.ts:210
src/request-pipeline/utils.ts:95
src/request-pipeline/destination-request/index.ts:171
npm i nock
Create
test.js
:node test.js
example.com
.The text was updated successfully, but these errors were encountered: