Hi Cristofer,

I can see where this would come in very handy in some situations like where the new page uses the same query string params, but not sure this is desirable in all cases. If the new page does not use the params it could hurt the SEO of the new page.

I made this change in my copy for the next release:

if (WebConfigSettings.PassQueryStringFor301Redirects)
            {
                app.Context.Response.AddHeader("Location", siteRoot + "/" + newUrl + app.Request.Url.Query);
            }
            else
            {
                app.Context.Response.AddHeader("Location", siteRoot + "/" + newUrl);
            }

so it will be possible to enable your scenario by adding a config setting while keeping the current behavior as the default.

Best,

Joe