From: Michael Olbrich <m.olbrich@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Ian Abbott <abbotti@mev.co.uk>
Subject: Re: [ptxdist] [APPLIED] nginx: Allow ngx_http_charset_module to be built
Date: Thu, 12 Sep 2024 14:11:58 +0200 [thread overview]
Message-ID: <20240912121158.2687973-1-m.olbrich@pengutronix.de> (raw)
In-Reply-To: <20240830132722.65713-1-abbotti@mev.co.uk>
Thanks, applied as 0d9b9bf68cdec06c8b93dfbc517e2bcd35291454.
Michael
[sent from post-receive hook]
On Thu, 12 Sep 2024 14:11:58 +0200, Ian Abbott <abbotti@mev.co.uk> wrote:
> Add a configuration option to build the http charset module. It allows a
> charset to be specified in the HTTP "Content-Type" header, for example
> for setting the charset to "utf-8".
>
> It can also do charset conversions with some limitations, but the
> nginx.make file has not been modified to install any of the supplied
> conversion tables.
>
> Signed-off-by: Ian Abbott <abbotti@mev.co.uk>
> Message-Id: <20240830132722.65713-1-abbotti@mev.co.uk>
> Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de>
>
> diff --git a/rules/nginx.in b/rules/nginx.in
> index ca043460c851..6ee8a2ec1cb8 100644
> --- a/rules/nginx.in
> +++ b/rules/nginx.in
> @@ -41,6 +41,14 @@ config NGINX_HTTP_AUTOINDEX_MODULE
> ngx_http_autoindex_module processes requests ending with the
> slash character and produces a directory listing.
>
> +config NGINX_HTTP_CHARSET_MODULE
> + bool
> + prompt "ngx_http_charset_module"
> + help
> + ngx_http_charset_module adds a charset to the "Content-Type"
> + response header field. The module can convert data from one
> + charset to another with some limitations.
> +
> config NGINX_HTTP_FASTCGI_MODULE
> bool
> prompt "ngx_http_fastcgi_module"
> diff --git a/rules/nginx.make b/rules/nginx.make
> index 5b5669de00a3..85df855e1d0e 100644
> --- a/rules/nginx.make
> +++ b/rules/nginx.make
> @@ -68,7 +68,7 @@ NGINX_CONF_OPT := \
> $(call ptx/ifdef, PTXCONF_NGINX_HTTP_V2_MODULE,--with-http_v2_module) \
> --with-http_sub_module \
> $(call ptx/ifdef, PTXCONF_NGINX_HTTP_GZIP_STATIC_MODULE,--with-http_gzip_static_module) \
> - --without-http_charset_module \
> + $(call ptx/ifdef, PTXCONF_NGINX_HTTP_CHARSET_MODULE,,--without-http_charset_module) \
> $(call ptx/ifdef, PTXCONF_NGINX_HTTP_GZIP_MODULE,,--without-http_gzip_module) \
> --without-http_ssi_module \
> --without-http_userid_module \
prev parent reply other threads:[~2024-09-12 12:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-30 13:27 [ptxdist] [PATCH] " Ian Abbott
2024-09-12 12:11 ` Michael Olbrich [this message]
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=20240912121158.2687973-1-m.olbrich@pengutronix.de \
--to=m.olbrich@pengutronix.de \
--cc=abbotti@mev.co.uk \
--cc=ptxdist@pengutronix.de \
/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