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

'INFO response dropped without fully consuming..' seen in successful / fully read requests #433

Open
samothx opened this issue Jan 2, 2024 · 0 comments
Open

'INFO response dropped without fully consuming..' seen in successful / fully read requests #433

samothx opened this issue Jan 2, 2024 · 0 comments

Comments

@samothx
Copy link

samothx commented Jan 2, 2024 •
edited
Loading

I see the above message in requests that are definitely fully read.
Looking at trace output it appears that this is internal to isahc and a hint is given by the following traces:

2024-01-03 08:43:59 TRACE [isahc::handler] << <html>\r\n<head><title>301 Moved Permanently</title></head>\r\n<body>\r\n<center><h1>301 Moved Permanently</h1></center>\r\n<hr><center>nginx/1.22.1</center>\r\n</body>\r\n</html>\r\n
2024-01-03 08:43:59 TRACE [isahc::handler] <- handler;
2024-01-03 08:43:59 TRACE [isahc::handler] write;
2024-01-03 08:43:59 TRACE [isahc::handler] -> write;
2024-01-03 08:43:59 TRACE [isahc::handler] received 169 bytes of data
2024-01-03 08:43:59 TRACE [isahc::handler] -> handler;
2024-01-03 08:43:59 TRACE [isahc::handler] <- handler;
2024-01-03 08:43:59 TRACE [isahc::client] -> send_async;
2024-01-03 08:43:59 TRACE [isahc::client] <- send_async;
2024-01-03 08:43:59 TRACE [isahc::client] -> send_async;
2024-01-03 08:43:59 TRACE [isahc::handler] -> handler;
2024-01-03 08:43:59 TRACE [isahc::handler] <- handler;
2024-01-03 08:43:59 TRACE [isahc::handler] -> handler;
2024-01-03 08:43:59 DEBUG [isahc::handler] TLSv1.3 (IN), TLS handshake, Encrypted Extensions (8):
2024-01-03 08:43:59 TRACE [isahc::handler] <- handler;
2024-01-03 08:43:59 TRACE [isahc::handler] -> handler;
2024-01-03 08:43:59 TRACE [isahc::handler] <- handler;
2024-01-03 08:43:59 DEBUG [isahc::handler] handler;
2024-01-03 08:43:59 TRACE [polling] Poller::notify()
2024-01-03 08:43:59 TRACE [polling::epoll] notify: epoll_fd=9, event_fd=10
2024-01-03 08:43:59 TRACE [isahc::client] <- send_async;
2024-01-03 08:43:59 TRACE [isahc::client] -> send_async;
2024-01-03 08:43:59 TRACE [isahc::client] <- send_async;
2024-01-03 08:43:59 TRACE [isahc::handler] -> handler;
2024-01-03 08:43:59 TRACE [isahc::handler] <- handler;
2024-01-03 08:43:59 INFO  response dropped without fully consuming the response body, connection won't be reused

I am thinking the unread response might be connected to the internal 301. The log probably contains output from several parallel requests so it is likely to be a little confusing.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@samothx