aboutsummaryrefslogtreecommitdiff
path: root/content/blog/miscellaneous/nginx-rewrite-break-last.md
diff options
context:
space:
mode:
authorJulien Dessaux2021-04-16 17:43:25 +0200
committerJulien Dessaux2021-04-16 17:43:25 +0200
commit88b281ef556b817b7d1ac14c34daa0e191b7c6e0 (patch)
tree1a6a0a8c8a9ee93b086f6f3e8c29116d17255f8f /content/blog/miscellaneous/nginx-rewrite-break-last.md
parentAdded articles (diff)
downloadwww-88b281ef556b817b7d1ac14c34daa0e191b7c6e0.tar.gz
www-88b281ef556b817b7d1ac14c34daa0e191b7c6e0.tar.bz2
www-88b281ef556b817b7d1ac14c34daa0e191b7c6e0.zip
Fixed nginx configurations syntax highlighting
Diffstat (limited to '')
-rw-r--r--content/blog/miscellaneous/nginx-rewrite-break-last.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/content/blog/miscellaneous/nginx-rewrite-break-last.md b/content/blog/miscellaneous/nginx-rewrite-break-last.md
index e5073a2..7cb854e 100644
--- a/content/blog/miscellaneous/nginx-rewrite-break-last.md
+++ b/content/blog/miscellaneous/nginx-rewrite-break-last.md
@@ -13,7 +13,7 @@ Today I was called in escalation to debug why a set of rewrites was suddenly mis
## Outside a location block
When used outside a location block, these keywords stop the rules evaluation and then evaluate to a location. Consider the following example :
-{{< highlight conf >}}
+{{< highlight nginx >}}
server {
[...]
location / {
@@ -48,7 +48,7 @@ configs # we hit the rewrite to /configs/test.cfg, which is then reevaluated an
When used inside a location block a rewrite rule flagged last will eventually trigger a location change (it is reevaluated based on the new url) but this does not happen when break is used.
Consider the following example :
-{{< highlight conf >}}
+{{< highlight nginx >}}
server {
[...]
location / {