ObjFW  History Of Ticket 5ad1ca4257

Artifacts Associated With Ticket 5ad1ca4257

1. Ticket change [79ae673c7c] (rid 39430) by js on 2022-09-12 09:05:11:

   1. icomment:

      When using `ofhttp` to download a file via HTTPS and ObjFW compiled with OpenSSL for OFTLSStream support, downloads sometimes hang. I collected a few reproducers, but none of them work anymore. However, this issue sporadically still happens. It seems to depend on certain network conditions.
      
      As a workaround, GnuTLS could be preferred over OpenSSL for 1.0, but then it's even less unlikely to find the root cause for this issue, so it might actually be good to release it with the broken OpenSSL support just to debug this further to fix it.
      

   2. login: "js"
   3. milestone initialized to: "1.0"
   4. mimetype: "text/x-markdown"
   5. priority initialized to: "High"
   6. severity initialized to: "Severe"
   7. status initialized to: "Open"
   8. title initialized to:

      OFTLSStream with OpenSSL implementation sometimes hangs
      

   9. type initialized to: "Code_Defect"

2. Ticket change [cde320a655] (rid 39431) by js on 2022-09-12 09:18:00:

   1. icomment:

      This seems to reproduce it (for now):
      
      ```
      ofhttp https://github.com/vector-im/element-web/releases/download/v1.11.4/element-v1.11.4.tar.gz
      ```
      

   2. login: "js"
   3. mimetype: "text/x-markdown"
   4. resolution changed to: "Open"

3. Ticket change [af2c3bb089] (rid 42291) by js on 2023-06-11 15:55:28:

   1. icomment:

      Can no longer be reproduced. Should be re-opened when a new reproducer is found.
      

   2. login: "js"
   3. mimetype: "text/x-markdown"
   4. resolution changed to: "Unable_To_Reproduce"
   5. status changed to: "Closed"

4. Ticket change [22afd23f09] (rid 42848) by js on 2023-08-27 09:26:41:

   1. icomment:

      This wasn't actually fixed: The problem only disappeared because `OFHTTPClient` switched to non-blocking sockets (which caused other problems). Reverting this change and using blocking sockets, this problem was back. However, it is now properly fixed by [](38e105d056).
      

   2. login: "js"
   3. mimetype: "text/x-markdown"
   4. resolution changed to: "Fixed"
   5. status changed to: "Fixed"