Conversation

Notices

1. Embed this notice
   Ryle (ryle@awoo.fyi)'s status on Thursday, 24-Nov-2022 05:39:55 JST Ryle

   in reply to

   • Alex Gleason
   • pawlicker
   • かわいい川獺
   We decided to go with a different provider but still using Cloudflare for caching in front of the S3 object storage, costs more though.
   
   Originally attempted to modify the code for this. However, some ACL things were baked right into the dependencies and from my rudimentary knowledge, it looked like the way forward was to fork the dependencies.
   
   I wasn't excited about the prospect, so I then looked at setting up a reverse HTTPS proxy that would strip the HTTP headers we didn't want. It almost worked, except the API wanted responses back; so, I stubbed some resposnes and then it got too complicated when not all stubbed responses worked quite right.
   
   It's not really a bug, but it would have been nice if Cloudflare just didn't throw any errors and just did enough to pretend/mock it supported those headers instead of throwing blatant error messages.
   • Alex Gleason likes this.
   • Embed this notice
     かわいい川獺 (kawaiiuso@outpoa.st)'s status on Thursday, 24-Nov-2022 05:39:57 JST かわいい川獺

     in reply to

     • Alex Gleason
     • pawlicker
     Cloudflare's really been hitting the shitter after the KF incident haven't they? Simple bugs like this are killer.
   • Embed this notice
     pawlicker (pawlicker@outpoa.st)'s status on Thursday, 24-Nov-2022 05:39:58 JST pawlicker

     • Alex Gleason
     Hey @alex a friend of mine was trying to set up a instance with Cloudflare r2 but it doesn't exactly work. He's filed a bug too about it.
     https://gitlab.com/soapbox-pub/rebased/-/issues/130
     
     Know any tips or workarounds?