One of our most frequently requested features is “automatic pass through” of query string parameters present on a URL covered by an HTTP 301 or 302 status redirect rule. We currently handle proxy redirects (HTTP 200 status) in this way, but not 301/302 redirects. For 301/302 redirects today, we ca…

For anyone struggling with this issue, here’s an edge function that fixes the problem. It detects the Netlify query string redirect behavior by comparing incoming request and outgoing response query params on 301s and 302s, and strips the query string the location header value if the parameters are …

Thanks much! I pinged the dev team to take a look. Not sure if it will be a quick fix but it is now on their radar. They’ll give updates in the issue as things, er, develop!

@fool So I am probably going about this wrong, but how do I redirect and NOT preserve the query params? Here is a demo site I created that only has the following redirects, and no javascript whatsoever. https://agitated-borg-b9f1bd.netlify.app/ # Pagination # redirect page 1 to route with no pag…

hi there, before we dig in, did you see this brand new guide on debugging redirects? I strongly suggest you give it a thorough read through and see if this fixes your problem: [image] [Support Guide] Making redirects work for you - troubleshooting and debugging Support Guid…

Thanks for the reply. I have read that article, and been through your docs on query params redirects. I may be missing something but I still don’t see an answer to my question. How can I make these redirects NOT preserve query params? /* page=1 /:splat 301! /* page=:page /:splat/:pag…

Or is there a better way to achieve the same result without the infinite redirect? I want any URL that has ?page=1 to redirect to the same URL but without ?page=1 And Any URL that has ?page={any other value} to redirect to the same URL but with /:page at the end and the page query string removed. …

Hey Rob! This is a very new change which I too am still familiarising with. I’ve set up a repro and I can also observe this. I’m not seeing a quick win so I’ll raise this internally to see what the wider team suggest. Thanks for bearing with us! @annejan , are you saying that the content on the pag…

@robmsw et al, I’ve filed an issue for our team to investigate. You can break the redirect loop, for now, by including a dummy query string param. @robmsw , your redirects therefore could look similar to this: /* page=1 /:splat?no-query-string 301! /* page=:page /:splat/:page?no-query-s…

@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!

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=:token…

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 J…

Changes to Redirects with query string parameters are coming

Features Updates

Topic		Replies	Views
Preserve query parameters on redirect Support redirects	69	22163	May 18, 2021
queryStringParameters not working with redirect on production Support lambda-functions , netlify-dev-open-beta , redirects	35	11032	November 27, 2022
Disable Netlify passing query params on 302 redirect Support lambda-functions , redirects , nextjs	3	738	February 13, 2025
Proxy redirect looses query parameters towards netlify function Support lambda-functions , proxying , redirects	8	1489	March 9, 2022
Keep incoming query string params and append a new param during redirect (instead of replacing) Support redirects	5	1852	July 12, 2021

Changes to Redirects with query string parameters are coming

Related topics