> I changed the client so it doesn't try to read the whole response before parsing > the header. And added timeout to make sure the connection is closed. This sounds like the way to go! You can't reply on the server being compliant. I wish we'd get a stream status code so you could know when to disable that, though... Also for the record, my Go clients never experience this "not closing the connection" issue. Amfora attempts to load all the data before displaying it (this will change), and I've never had any problems with that on any servers. It always finds the end of the data fine, presumably indicated by a closed connection. Maybe the Go TLS implementation is just more robust? makeworld
---
Previous in thread (9 of 16): 🗣️ Petite Abeille (petite.abeille (a) gmail.com)
Next in thread (11 of 16): 🗣️ Petite Abeille (petite.abeille (a) gmail.com)