### Category WiFi ### Hardware Heltec V3 ### Firmware Version 2.5.11.8e2a3e5 ### Description Chrome (~90 seconds): https://github.com/user-attachments/assets/6945fdc0-bc10-4005-93c8-74faf714507e Firefox (~4 seconds): https://github.com/user-attachments/assets/60737f5f-e9b8-48ba-b4e9-88adb8af74ee I think this is because Chrome re-establishes the connection (TCP+TLS) for each request: <img width="1624" alt="Screenshot 2024-11-17 at 3 17 12 PM" src="https://github.com/user-attachments/assets/c67bb323-f6a5-4379-9af7-b118acd527c7"> <img width="1624" alt="Screenshot 2024-11-17 at 3 18 42 PM" src="https://github.com/user-attachments/assets/ed3d6bf0-5641-4cba-a701-a573a130aaa0"> Connection keep-alive is supposed to work, and make a huge difference, as seen in Firefox, where each request takes only ~60 ms. I thought I figured out the reason Chrome connections don't keep alive but I found some conflicting clues so now I'm not so sure I understand why. ### Relevant log output _No response_
Category
WiFi
Hardware
Heltec V3
Firmware Version
2.5.11.8e2a3e5
Description
Chrome (~90 seconds):
Screen.Recording.2024-11-17.at.2.51.14.PM.1.mov
Firefox (~4 seconds):
Screen.Recording.2024-11-17.at.2.59.48.PM.1.mov
I think this is because Chrome re-establishes the connection (TCP+TLS) for each request:
Connection keep-alive is supposed to work, and make a huge difference, as seen in Firefox, where each request takes only ~60 ms.
I thought I figured out the reason Chrome connections don't keep alive but I found some conflicting clues so now I'm not so sure I understand why.
Relevant log output
No response