vvo459

Hello Stefan thanks for your swift reply! Yeah, unfortunately it was also us who reported issue #231 ;) daum3ns is a colleague of mine and we worked together on that...

First one correction: When analyzing the logs again I saw that the very first canceled SSE Stream indeed ends with a "destroy" ``` 2022-05-12 10:50:18.143721 http2:trace2 10.16.12.58:59119 h2_stream(1032-13,CLEANUP): cleanup ......

"When the h2 connection sees behaviour that it regards as an attempt by the client to hog its resources,.." For example sending an RST frame correct? "but on the first...

"Sending RST before a single byte of the response was sent. After that, it's fine. The propose line removal changes that to: RST is fine as long as the client...

Unfortunately, this time the fix did not help. From the clients side the effect was quite the same: 16 canceled requests by the client again lead to a blocking of...

Yeah you are absolutely right. I just saw the message did not get sent for some reason ("Delivery expired"), just got the notification in my inbox on saturday. I will...

I hope in the meantime you received our logs, we tried with an other email address from our side. In the meantime, the application developers changed tha application a bit:...

_I found the access information in my spam folder, but the download gives a 500 page on your server. It seems a bit cursed._ Probably now the download link expired....

For me, this workaround helped: import "github.com/andybalholm/brotli" c.OnResponse(func(r *colly.Response) { .... if contentEncodingHeader == "br" { bodyReader := bytes.NewReader(r.Body) brReader := brotli.NewReader(bodyReader) decompressed, err := io.ReadAll(brReader) if err != nil...