@Scott thanks for the help, adding that parameter in does break the loop and having the null=null in the url should be fine for my current use case. Thanks!
1 Like
I am attempting to configure a simple redirect which takes path parameters and exposes them as querystrings.
The configuration looks as follows and by my understanding should work
[[redirects]]
from = "/api/meta/:symbol/:tokenId"
to = "/.netlify/functions/meta?symbol=:symbol&tokenId=:tokenId"
force = true
status = 200
However when hitting the endpoint /api/meta/symbol/123 no querystrings are received by the function.
If I instead use /api/meta/symbol/123?symbol=sym&tokenId=123 they are.
Why does the redirect rule not correctly package the querystring values?
Hi @eddyoc,
To pass query strings like this, you’d need a 301 redirect. For example, you can check this out: https://hungry-austin-248205.netlify.app/. Add any path to it like: https://hungry-austin-248205.netlify.app/foo/bar and you’d see the query string received by the function. It’s just doing JSON.stringify(event.queryStringParameters).
If you don’t wish to expose your function endpoint, you’d have to do another 301 back to the page that called it, but you probably won’t be able to return a JSON response this way. The recommended way to use query parameters with functions is the way you have already mentioned.
You can just do /api/meta/?symbol=sym&tokenId=123 and the query string will be received by the meta function.