Go functions don't seem to work correctly for wildcard routes

[roblillack (Rob L.)]

Given a Go function called /api/[...path].go, all requests like /api/login, /api/user, etc. are routed correctly and handled by the function.

Alas, all routes three levels deep (/api/user/verify, /api/shizzle/{id}) instantly return a 404. They do not even show up in the logs.

In that regard, it looks like the platform handles Go functions with a wildcard name [...path] as if it was named just [path].

This looks like a bug to me.

[system]

There’s another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes.

Debugging 404 Errors

Sometimes things don’t go as expected when deploying a website. If you see a 404 on your site, that means the page or resource couldn’t be found. There are many possible causes, and the absence of something can be tricky debug if you don’t know where to look. Here are some things you can do to find the cause and fix it. Debugging Tips Check the error code If you see a mostly white screen with 404: NOT_FOUND along with a Code and and ID then you can click the blue info box below the error deta…

A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.

[jacobparis]

Thanks for reporting, I can reproduce this. I’ll share this internally

[roblillack (Rob L.)]

Thanks @jacobparis, please keep me updated about the status of this issue!