Today I was reminded that HTTP/2 servers can deny communication quite unceremoniously by sending back a #GOAWAY signal. What do you do to resume communication? Simply retry the request? Or also refresh the #HTTP client that makes the requests?
Conversation
Notices
-
Ænðr E. Feldstraw (aeveltstra@mastodon.social)'s status on Friday, 10-Mar-2023 06:46:05 JST Ænðr E. Feldstraw - Adrian Cochrane repeated this.
-
Ænðr E. Feldstraw (aeveltstra@mastodon.social)'s status on Friday, 10-Mar-2023 06:46:05 JST Ænðr E. Feldstraw #NGINX and other #HTTP servers will throw a fit if a client sends 1000 requests, and literally tell the client to go away. In the #java programming language, the #HttpClient built into the #jdk throws an IOException, without any further specialization. The #Jetty client for HTTP/2 does throw a specific error and also indicates the lost frame ID, for easy resumes. I guess we could switch clients, or I could find a nice way to catch this error and resume communications. Any suggestions?