From 88b281ef556b817b7d1ac14c34daa0e191b7c6e0 Mon Sep 17 00:00:00 2001 From: Julien Dessaux Date: Fri, 16 Apr 2021 17:43:25 +0200 Subject: Fixed nginx configurations syntax highlighting --- content/blog/miscellaneous/nginx-ldap.md | 2 +- content/blog/miscellaneous/nginx-rewrite-break-last.md | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) (limited to 'content/blog/miscellaneous') diff --git a/content/blog/miscellaneous/nginx-ldap.md b/content/blog/miscellaneous/nginx-ldap.md index e9135c7..deea4a4 100644 --- a/content/blog/miscellaneous/nginx-ldap.md +++ b/content/blog/miscellaneous/nginx-ldap.md @@ -8,7 +8,7 @@ tags: ## How to -{{< highlight sh >}} +{{< highlight nginx >}} ldap_server ldap { auth_ldap_cache_enabled on; auth_ldap_cache_expiration_time 10000; 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 / { -- cgit v1.2.3