This error mysteriously resolved itself at 13:22 UTC today. The above is the last appearance of the error. Was there anything weird going on with release.lucee.org yesterday/today?
I’m unsure what status code was being returned but it was not a 200 apparently. It wasn’t enough to throw an exception since that’s trapped in the earlier code block.
Thank you! It does look like they did some major work over the past 24 hours. And the release.lucee.org dns entry points to the same place as download.lucee.org so I’m somewhat confident it’s the same service behind the scenes. Thank you for pointing out this repo and the activity. Seems plausible to me that there might have been a few issues that they introduced and then fixed.