Closed YarnSeemannsgarn closed 6 years ago
I think this is the issue.
Actually my code worked after some tries. The problem is that if the internet connection gets interrupted, this error will appear. It is not catchable from my code and needs to be handled in this repository:
That is a good point @YarnSeemannsgarn. I was only listening for errors on the parsing, not on the network stream. I just pushed a fix for this. You will get a regular callback with the network error.
Thanks for reporting this!
Just published version 1.4.0 to npm
"In my case I was able to workaround the problem by setting the Connection: keep-alive header." https://github.com/request/request/issues/2047
There is some more good stuff!
I see that header is already integrated..nice
I tried the parser for booking.com with the following code:
The parser runs a while, but then stops with the following error