summaryrefslogtreecommitdiff
path: root/pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
diff options
context:
space:
mode:
authorDave Nicponski <dave.nicponski@gmail.com>2022-10-12 19:47:36 -0400
committerDave Nicponski <dave.nicponski@gmail.com>2022-10-20 10:59:28 -0400
commit1a73877305f32ff158173878dda6b86f378ff3c8 (patch)
tree0e4b532ed400429b26b03ecba89d103315e47074 /pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch
parentbbbaaa3e3530335bdefa5d4e682e3f1b4fbf218c (diff)
Tweak nginx config for Let's Encrypt ACME challenges
Currently, this is using a "URI prefix match", but per nginx docs, ``` [...] the location with the longest matching prefix is selected and remembered. Then regular expressions are checked, in the order of their appearance in the configuration file. The search of regular expressions terminates on the first match, and the corresponding configuration is used. If no match with a regular expression is found then the configuration of the prefix location remembered earlier is used. ``` which means a config like this (from wordpress service) will override that ``` locations = { "~ /\\." = { priority = 800; extraConfig = "deny all;"; }; }; ``` 😱 Luckily, from nginx docs: ``` If the longest matching prefix location has the “^~” modifier then regular expressions are not checked. ``` Whew!
Diffstat (limited to 'pkgs/development/python-modules/python-mapnik/python-mapnik_std_optional.patch')
0 files changed, 0 insertions, 0 deletions