Proxy redirect looses query parameters towards netlify function

Support
, ,
1

Lately our proxy redirect settings are not able to read the incoming query parameters in the netlify function.
The proxy redirect still works, but the query params are empty in the request. This has stopped working since one week ago.

Working:
https://raket-test.netlify.app/.netlify/functions/next_s_shopId_sellerId_path?qool=123
Not Working:
https://main.raket.nu/sv-se/shop/.netlify/functions/next_s_shopId_sellerId_path?qool=123

[[redirects]]
  from = "/sv-se/shop/*"
  to = "https://raket-test.netlify.app/:splat"
  status = 200
  force = true

What has been changed lately, or is my 1 year old proxy setting wrong?

2

According to the document this should not be a problem:

While our service automatically passes on all query string parameters to destination paths for redirects with 200 , 301 , and 302 HTTP status, you can also choose to define a redirect path based on a specific parameter or combination of parameters.

When proxying to a different application thats not on Netlify, the query parameters where available.
So its only when proxying to an other Netlify domain with an Netlify function.

4

Hey @raketwebbyra,

Are you able to access query parameters for rewrites on the same site? I think the query strings are not passed along with it’s a cross-site rewrite. It works fine for the same-site. Could you try that on your end too?

6

Yes! When rewriting from the same site it works as expected, but when there is a proxy rewrite first, the query params gets lost. And this has not been an issue before.

7

We’re seeing the same thing. This was working previously.

9

Hey all,

We’ve filed an issue for the engineers to look at this and we would update as things develop.

2 Likes
10

Just want to jump on the train and say its not just you, I’ve spent the entire morning trying to debug this problem that exists on a 10 month old working solution only to now find your post and realise its something on the netlify side

11

It seems like its started to work again, but it has not been confirmed by an Support Engineer yet :slight_smile:

12

Hi everyone,

The fix for this was deployed across the CDN yesterday. Let us know if it’s still giving issues.

1 Like