Francis Daly Wrote: > In this case, it looks to me that you can probably "return" rather > than > "rewrite", since everything should probably be a http redirect. > non-Mediawiki URL > [...] Except I would have the config be not a lot more than > > location = /wiki/index.php { return 301 > https://example.net/$my_static_wiki; } > mby petecooper - Nginx Mailing List - English
Hello. I'm diverting traffic from an retired MediaWiki site to an active static site. I'm somewhat confused with the process of `rewrite`-ing old URLs with a query string to standard URLs *without* a query string on the static site. For clarity, I do not need or want query strings on the new site. Retired URLs examples: https://example.com/wiki/index.php?title=en/Main_Page https://by petecooper - Nginx Mailing List - English
Hello. I am compiling Nginx 1.14.0 from source on Ubuntu 18.04 LTS with a view to compiling ipscrub as a dynamic module. My compile completes without error, my nginx.conf validates, Nginx runs as expected, yet my server block throws an error about an unknown log format. If my `log_format` directive appears after the `access_log` directive in nginx.conf, it will not validate, stating: ngiby petecooper - Nginx Mailing List - English
Hello. I am compiling Nginx 1.14.0 from source with a view to compiling ipscrub as a dynamic module. My compile completes without error, my nginx.conf validates, Nginx runs as expected, yet my server block throws an error about an unknown log format. If my `log_format` directive appears after the `access_log` directive in nginx.conf, it will not validate, stating: nginx: unknown logby petecooper - How to...
![]() |
![]() |
![]() |
![]() |
|