Netlify redirect shows strange behaviour

Hi,

We have a redirect file on cnnct-cloud-redirect.netlify.app that has a few redirect options, but somehow it doesn’t always work as expected. This is our setup in the toml file.

[[redirects]]
	from = "/not-active"
	to = "/index.html"
	status = 200

[[redirects]]
	from = "/*"
	to = "https://sense.tpp.onl/"
	status = 302
	force = true
	query = { u=":u" }

[[redirects]]
	from = "/"
	to = "https://tapp.online/"
	status = 302
	force = true

[[redirects]]
	from = "/*"
	to = "/.netlify/functions/redirect"
	status = 200

– The last redirect rule points to a function that checks with our database where the user should be redirected to.

– The base url is redirected to https://tapp.online/.

– And all incoming urls containing ?u=... should be redirected to https://sense.tpp.onl, which most of the times does work. But lately we’ve encountered situations where these type of urls are redirected to the weirdly specific https://tapp.online/home/no-limits-to-data/?u=… instead. After redeploying and clearing the cache it seemed to be solved, but then we encountered the same issue again after a few days.

Any help figuring this out is appreciated.
Kind regards,
Fabian

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:

if not, please post again, and we’ll try and troubleshoot.

Well the issue is not so much that the redirects don’t work, they fundamentally do and have been for a long time. The issue is that they now seem to randomly show unexpected behaviour. This can vary between subsequent visits of the same url, switching between working correctly and behaving unexpectedly.

Hi, @fabianhijlkema. It appears there is a support ticket for this same issue. I’ve replied to the support ticket with a question for you.

I would recommend replying there as we can share information more freely in a private conversation. However, please feel free to reply here if you prefer (and certainly reply here if you don’t see our reply on the support ticket).