Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Multipart response whose connection gets killed is still written to WARC #450

Open
JustAnotherArchivist opened this issue Apr 5, 2020 · 0 comments
Open

Multipart response whose connection gets killed is still written to WARC #450

JustAnotherArchivist opened this issue Apr 5, 2020 · 0 comments
Labels
bug
Projects
Network stack issues in 2.0.x

Comments

@JustAnotherArchivist
Copy link
Contributor

Occasionally, responses are still written to WARC after the connection is killed. This happened for example just now on AB job f2ptcvfs97x6crtgda8lt9ed2.

2020-04-05 20:19:02,834 - wpull.processor.web - INFO - Fetched ‘http://webcam.trebic.cz:8081/axis-cgi/mjpg/video.cgi?resolution=640x480&dummy=1563608699660’: 200 OK. Length: unspecified [multipart/x-mixed-replace; boundary=--myboundary].

I've only seen this happen for such multipart responses of webcams, so I suspect it has something to do with that.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
Network stack issues in 2.0.x
  
To do
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JustAnotherArchivist