3 ms·

I understand the server is having difficulties, but this is the first time I see "406 - not acceptable" in the wild. I expected it to throw a 500 error or just

• mcv 4y ago
  Maybe it didn't go down because it maintains a hard limit on how many requests it considers acceptable? Any request beyond that number is not a bad request per se, but still unacceptable to the server. That's the best logic I can discern here. I honestly have no idea.
  • account42 4y ago
    That would not be a proper use of the 406 code, which is specifically about the Accept* headers that the client sent. My guess would be that whatever abstraction they used ended up with no content produced (because of timeout or whatever) so the framework could not satisfy any of the content types that the client accepts. Still another error would be better but I can see how it could happen.
• kapilkale 4y ago
  That makes two of us. We have a Cloudflare worker serve the content from Webflow (which is actually set up with a custom domain at https://webflow2.tremendous.com/ https://webflow2.tremendous.com/. Yes, it's a little convoluted. We still don't know what broke here - the Cloudflare worker or Webflow, or the combination of the two.