Taildrop: fails when sending many files from macOS #5873
Description
What is the issue?
I'm sending from iOS (1.30.2) to a Windows (1.30.1) machine.
On the Windows machine, I see:
2022-10-07 17:54:41.9334572 -0700 PDT: peerapi: put Copy error: unexpected EOF
2022-10-07 17:54:41.9334572 -0700 PDT: peerapi: put Copy error: unexpected EOF
2022-10-07 17:54:41.9334572 -0700 PDT: peerapi: put Copy error: unexpected EOF
2022-10-07 17:54:41.935013 -0700 PDT: peerapi: put Copy error: unexpected EOF
2022-10-07 17:54:41.9373942 -0700 PDT: peerapi: put Copy error: unexpected EOF
2022-10-07 17:54:41.9560422 -0700 PDT: peerapi: put Copy error: unexpected EOF
2022-10-07 17:54:42.3082423 -0700 PDT: peerapi: put Copy error: unexpected EOF
2022-10-07 17:54:42.3154549 -0700 PDT: peerapi: put Copy error: unexpected EOF
2022-10-07 17:54:42.3278697 -0700 PDT: peerapi: put Copy error: unexpected EOF
2022-10-07 17:54:42.5259584 -0700 PDT: peerapi: put Copy error: unexpected EOF
2022-10-07 17:54:42.5514431 -0700 PDT: peerapi: put Copy error: unexpected EOF
On the iOS device, I see:
2022-10-08 00:54:41.099811 +0000 UTC: http: proxy error: readfrom tcp 100.76.79.70:59682->100.107.177.2:33542: write tcp 100.76.79.70:59682->100.107.177.2:33542: write: no buffer space available
2022-10-08 00:54:41.109393 +0000 UTC: http: proxy error: readfrom tcp 100.76.79.70:59789->100.107.177.2:33542: write tcp 100.76.79.70:59789->100.107.177.2:33542: write: no buffer space available
2022-10-08 00:54:41.109466 +0000 UTC: http: proxy error: readfrom tcp 100.76.79.70:59791->100.107.177.2:33542: write tcp 100.76.79.70:59791->100.107.177.2:33542: write: no buffer space available
2022-10-08 00:54:41.109519 +0000 UTC: http: proxy error: readfrom tcp 100.76.79.70:59790->100.107.177.2:33542: write tcp 100.76.79.70:59790->100.107.177.2:33542: write: no buffer space available
2022-10-08 00:54:41.109614 +0000 UTC: http: proxy error: readfrom tcp 100.76.79.70:59792->100.107.177.2:33542: write tcp 100.76.79.70:59792->100.107.177.2:33542: write: no buffer space available
2022-10-08 00:54:41.109695 +0000 UTC: http: proxy error: readfrom tcp 100.76.79.70:59793->100.107.177.2:33542: write tcp 100.76.79.70:59793->100.107.177.2:33542: write: no buffer space available
2022-10-08 00:54:41.109772 +0000 UTC: http: proxy error: readfrom tcp 100.76.79.70:59795->100.107.177.2:33542: write tcp 100.76.79.70:59795->100.107.177.2:33542: write: no buffer space available
2022-10-08 00:54:41.109839 +0000 UTC: http: proxy error: readfrom tcp 100.76.79.70:59794->100.107.177.2:33542: write tcp 100.76.79.70:59794->100.107.177.2:33542: write: no buffer space available
2022-10-08 00:54:41.109919 +0000 UTC: http: proxy error: readfrom tcp 100.76.79.70:59796->100.107.177.2:33542: write tcp 100.76.79.70:59796->100.107.177.2:33542: write: no buffer space available
2022-10-08 00:54:41.11153 +0000 UTC: http: proxy error: readfrom tcp 100.76.79.70:59688->100.107.177.2:33542: write tcp 100.76.79.70:59688->100.107.177.2:33542: write: no buffer space available
2022-10-08 00:54:41.111952 +0000 UTC: http: proxy error: readfrom tcp 100.76.79.70:59862->100.107.177.2:33542: write tcp 100.76.79.70:59862->100.107.177.2:33542: write: no buffer space available
It appears that we are creating a new TCP connection for every file upload? Perhaps we should switch to a multipart HTTP POST?
Steps to reproduce
No response
Are there any recent changes that introduced the issue?
No response
OS
No response
OS version
No response
Tailscale version
No response
Bug report
No response