https://discord.cloudflare.com logo
Join Discord
Powered by
# functions
  • j
    Happy to share code if it helps, just wondering if anyone else sees that and immediately goes "aha, I know what that is"
  • i
    How are you doing 
    await next()
    if it's on a different route?
  • i
    IIRC that only gets the asset that's on the same route as you did the request on, and you need to use env.ASSETS.fetch() otherwise.
  • j
    Copy code
    const lookupFile = new URL(request.url);
lookupFile.pathname = './test.html';
const asset = await next(lookupFile);
  • j
    oh I can't do that?
  • i
    Oh. I'd try actually looking it up in env.ASSETS.fetch yourself.
  • i
    Although Walshy might have another option 🙂
  • j
    Same behaviour - 301s to whatever asset I fetch. Weird
  • w
    You can do 
    next(string)
    though not sure the behaviour compared the ASSETS.fetch
  • i
    Are you returning the response from next() without any modifications?
  • j
    Yep right now I'm checking if there's a query param 
    q
    , if so, trying to request a new asset, and then returning it, otherwise just passing through 
    next()
    . I want to change the html file I serve without altering the URL
  • i
    Huh... I have no clue then, sorry 😅
  • j
    I think I'm missing something obvious, but the docs for how 
    next
    works aren't super verbose yet
  • w
    well
  • w
    we redirect files to without their extensions
  • w
    I wouldn't expect that on assets.fetch but err
  • w
    what happens if you do just /test
  • j
    oh geez, lemme check
  • j
    yeah that worked perfectly. Sounds like a bug 😅
  • j
    Thanks @Walshy | Pages 🙂 Not sure if that's a runtime bug, or wrangler specific - want me to file or you got it?
  • w
    check if the 301 happens in prod and if it doesn't file a bug
  • j
    I always find the most obscure bugs, I'm sorry 😅
  • k
    Couldn't break the demo so you broke Functions
  • k
    You can't be left unsupervised
  • j
    Thankfully fast builds are making testing this nice and quick. Though logs would be quicker 😄
  • k
  • k
    put 'logs access' into that contract
  • j
    https://github.com/Cherry/universe-horse-test works perfectly locally with 
    npx wrangler@beta pages dev ./public
    , but https://universe-horse-test.pages.dev/?test 406's in prod. 🤔
  • j
    406 occurs with both 
    ./test.html
    and 
    ./test
    . Hmm
  • i
    The only thing I can think of there is that you're reconstructing a 
    new URL
    twice.
1...122123124...392Latest