From: Julien Olivain via buildroot <buildroot@buildroot.org>
To: "Raphaël Mélotte" <raphael.melotte@mind.be>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH 1/2] support/testing: add new test for nginx-modsecurity
Date: Sat, 28 Jun 2025 14:22:18 +0200 [thread overview]
Message-ID: <08585e4962ffe98f9faa307813c19ddc@free.fr> (raw)
In-Reply-To: <20250627121948.1933049-1-raphael.melotte@mind.be>
On 27/06/2025 14:19, Raphaël Mélotte via buildroot wrote:
> This test verifies that we can run nginx with the modsecurity
> directives.
> It also checks a very simple rule that blocks requests containing the
> keyword "blockme".
>
> Signed-off-by: Raphaël Mélotte <raphael.melotte@mind.be>
Series applied to master, thanks.
For info, I did few minor changes, see:
https://gitlab.com/buildroot.org/buildroot/-/commit/5cda85cb566bfcd9d7a6c5bd701d326a47cb725b
Best regards,
Julien.
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2025-06-28 12:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-27 12:19 [Buildroot] [PATCH 1/2] support/testing: add new test for nginx-modsecurity Raphaël Mélotte via buildroot
2025-06-27 12:19 ` [Buildroot] [PATCH 2/2] package/nginx-modsecurity: bump to version 1.0.4 Raphaël Mélotte via buildroot
2025-06-28 12:22 ` Julien Olivain via buildroot [this message]
2025-06-30 13:38 ` [Buildroot] [PATCH 1/2] support/testing: add new test for nginx-modsecurity Raphaël Mélotte via buildroot
2025-07-04 6:47 ` Thomas Perale via buildroot
2025-07-04 6:48 ` Thomas Perale via buildroot
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=08585e4962ffe98f9faa307813c19ddc@free.fr \
--to=buildroot@buildroot.org \
--cc=ju.o@free.fr \
--cc=raphael.melotte@mind.be \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox