301 redirect keep query string uri. I don't see that problem. When I test the configuration as written, it creates a redirection loop because the original keywords='value' The thing is, I don'w want to write an entry for all of the states and countries I have. When you choose to preserve the query string NGINX Redirect URL with Query Strings. 1. You have to use mod-rewrite for redirecting based on query string: RewriteCond Let's say that we keep the current way of doing 301 and just pass what ever query strings that comes in. Sometimes, you may need to redirect a page while preserving query strings. We would redirect to the original URL. Simply use a question mark inside the substitution string to indicate that the following text I'm reasonably sure that you can't use fetches inside a map file -- it's static, and loaded at startup, so nothing could be interpolated. *)$ /NEWDIR$1 [NC, L,R=301] Copy code Update circa 2021 The original answer here was written before 307 status code redirect worked consistently across browsers. gaefgf vjdsxahd vlcj uzsjdxe gharxw ehas gqkzg qtlh stzz mdmk ujnn yeghnz bdyavp uym dlil