https://discord.cloudflare.com logo
Join Discord
Powered by
# workers-discussions
  • g
  • m
    Ok, so if I understand this correctly the content will be encoded if I set the Content-Encoding header to either 'gzip' or 'br'. Does that mean that I am responsible for checking the Accept-Encoding header? I was expecting that compression would be handled automatically based on the supported encoding of the client.
  • g
    Ah, sorry, I misunderstood. Thought you meant "how can I serve up something that's already brotli/gzip encoded". But instead, you're asking "why doesn't Workers automatically handle compression of the response automatically"?
  • m
    Correct.
  • m
    I was expecting Workers to automatically compress responses based on the content-type and accept-encoding header of the client.
  • g
    I think because you're responsible for creating the Response from whatever Request you're handling, you're also responsible for setting the 
    Content-Encoding
    .
  • g
    So, this does work if you just pass in 
    new Response('hi', { headers: {'Content-Encoding': 'gzip'}})
  • g
  • g
    Side note: we need a bot for sharing Workers on cloudflareworkers.com
  • m
    Thank you @User for your assistance again! I did a quick test and this seems to work :).
  • w
    wait i did not know this was a thing
  • a
    How big is the response? Below a threshold it doesn't compress.
  • m
    That was the issue.. It’s like you read my mind. You’re not, right?
  • m
    It started working when I added some proper data and the response became larger than the basic tests I was doing.
  • m
    👋 Is there a clean/recommended way to respond to a request, and then fire off some followup requests after?
  • g
  • g
  • m
    Legend, ty!
  • m
    Is there a way to block the logic in 
    waitUntil
    until the original response has been sent?
  • g
    Not really, I don't think. You could probably do a hacky Promise sleep, but I think you'd be best just calling 
    waitUntil
    right before returning the Response in 
    respondWith
    . Why is it that you need to wait anyway?
  • m
    Sending messages to Discord in the right order -- my logic in waitUntil is managing to get a message to Discord before the respond to the original request gets there. I'm calling 
    waitUntil
    on the last line before the response already :/
  • g
    Haha, are we all working on Discord bots right now?
  • m
  • g
    Maybe a hacky sleep is the answer, then? Just a 300ms wait or something to let the Response get delivered
  • m
    Oh, can a setTimeout in waitUntil go beyond the 10ms limit for the worker?
  • m
    Oh yup I can't read docs
  • g
  • g
    That'll hold off 3 seconds before making the 
    followupRequests
  • g
    If it's just a slash command you're working on though, can you not just return the message as a response to the request?
  • g
    That's literally what I am coding right now
1...515253...2509Latest