ource \
--without-http_empty_gif_module \
--without-http_scgi_module \
--without-http_ssi_module \
--without-http_uwsgi_module \
--without-mail_imap_module \
--without-mail_pop3_module \
--without-mail_smtp_module
Here is the final part of the `make` output (formatted here
https://gist.github.com/petecooper/26e
petecooper Wrote:
---
> Hello.
> I have a single-digit fleet of Ubuntu servers, all running a similar
> configuration:
>
> * Ubuntu 20.04LTS, current kernel via `apt`
> * Nginx 1.23.1 from source, with 3rd party modules
&g
petecooper Wrote:
---
> Hello.
> I have a single-digit fleet of Ubuntu servers, all running a similar
> configuration:
>
> * Ubuntu 20.04LTS, current kernel via `apt`
> * Nginx 1.23.1 from source, with 3rd party modules
&g
Sergey A. Osokin Wrote:
---
Hello Sergey.
Thank you for your reply.
> On Sat, Aug 13, 2022 at 04:01:19AM -0400, petecooper wrote:
> > Hello.
> > I have a single-digit fleet of Ubuntu servers, all running a similar
&g
Hello.
I have a single-digit fleet of Ubuntu servers, all running a similar
configuration:
* Ubuntu 20.04LTS, current kernel via `apt`
* Nginx 1.23.1 from source, with 3rd party modules
* PHP 8.0 or 8.1 from source
One of the servers has recently had issues with what appears to be an Nginx
I run a fleet of small- to medium-scale web apps on PHP, and I'm comfortable
compiling Nginx + PHP to to optimise for my needs. Until now, I've used
PHP-FPM exclusively. I have read about performance improvements with Nginx
Unit as far as PHP is concerned. This interests me, and I have time
availab
Please ignore this thread, I found the answer:
https://trac.nginx.org/nginx/ticket/1529#comment:1
Thank you.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,293703,293705#msg-293705
___
nginx mailing list -- nginx@nginx.org
To unsubscribe s
I am following up with fresh eyes.The 3x ciphers that cause problems are:
TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY1305_SHA256
I have just noticed each cipher name above has an underscore `_` character
as a separator. The working ciphers all use a dash `-` as a separator.
M
Hello.
I am running Nginx 1.21.6 with OpenSSL 3.0.1 and the Mozilla [1] 'Modern'
ciphers 4.0 without issue. When I change the ciphers to Mozilla 'modern'
5.5, Nginx fails a config test with:
nginx: [emerg]
SSL_CTX_set_cipher_list("TLS_AES_128_GCM_SHA256:TLS_AES_256_GCM_SHA384:TLS_CHACHA20_POLY13
I am attempting to compile Nginx 1.21.3 with libdeflate[1] with a view to
comparing performance against classic Zlib and the Cloudflare fork of
Zlib[2].
I can successfully compile Nginx with classic Zlib. I can also successfully
compile Nginx with Cloudflare Zlib. I cannot yet compile Nginx with
l
Hello.
Per the documentation:
> $ssl_cipher
> returns the name of the cipher used for an established SSL connection.
This means `$ssl_cipher` returns e.g `TLS_CHACHA20_POLY1305_SHA256`.
Is it possible to return the corresponding hex value e.g. `0x1303` instead?
Thank you, and best wishes.
Post
Hello Maxim.
> nginx does not care if the upstream socket is reacheable or not
> when it parses configuration, it is only important when processing
> a particular request. That is, nginx can (and will) start just
> fine if the socket doesn't exist (or, similarly, upstream server's
> IP addres
Hello.
I have some servers running PHP applications on Nginx via PHP-FPM. Each
server uses a named socket in the filesystem. Nginx can often pass its
configuration test but the server does not function as expected if the named
socket file is not there (i.e. PHP-FPM is not running as expected).
Is
I compile Nginx from mainline source and update shortly after each
patch/point release. As part of the compile process, I obtain the current
OpenSSL source and bake that in with these compile flags:
--with-openssl-opt="enable-ec_nistp_64_gcc_128 shared no-ssl2 no-ssl3
no-weak-ssl-ciphers -fstack-p
e extra question mark out of your try_files line. It should
> look
> like this:
>
> try_files $uri $uri/ /index.php$is_args$args;
Perfect. That was it! Solved.
Thank you very much for your time and assistance, I am most grateful.
Best wishes to you.
Pete
> On Wed, May 27, 2020 at 9:33 A
Hello.
I run a PHP + MySQL content management system on Nginx (1.19.0 at time of
writing) and an issue has arisen with the way I'm handing PHP files in some
situations.
The issue appears to manifest with queries when they are prepended by a
path, where a `?` is prepended. If the queries exist in
Hi Francis.
Francis Daly Wrote:
---
> I suggest that you'll be happier in the long run using a templating
> language, or macro-substituting language, external to nginx; along
> with
> "source" conf files that are to have the substitutions applied
I compile Nginx mainline from source and update every release. I run a small
fleet of open source project and some small business Linux servers with
multiple websites per server. There are occasions when a site is taken down
for maintenance (typically minutes or hours of downtime out of peak hours)
Francis Daly Wrote:
---
> Do you know whether the file that corresponds to the url /index.php
> exists?
>
> If it does exist, use
>
> try_files $uri $uri/ /index.php?$args;
>
> If it does not exist, use
>
> try_files $uri $uri/ =404;
Hel
Hello.
I've got into knots with `try_files` inside `location` when PHP is
involved.
Ideally, I would like the following route for `try_files` (in order):
* $uri (requested URI)
* $uri/ (requested URI, trailing slash)
* /index.php?$args (use root `index.php` with args)
* =404 (Nginx returns 404)
Hello.
I use `add_header` to build Content Security Policy and Feature Policy
headers. To help with change control and maintainability I build an Nginx
variable from nothing and add each Content Security Policy and Feature
Policy data/source type on a different line. The Nginx variable is unique t
Francis Daly Wrote:
---
> It seems to work for me:
>
> "xml" should have 0s, so now.
> "rss" should have 1h.
> "png" should have 1M.
>
> $ curl -s -i http://127.0.0.1/a.xml | grep '^Content-Type\|^Expires'
> Content-Type: text/xml
> Expires: Tu
Hello.
I am attempting to use `expires` on Nginx 1.15.3 to define the expiry of
files on a per MIME type basis.
I have used [1] as a base, and constructed the following `map` in the `http`
section of a `include`-d `server` block (domain sanitised):
map $sent_http_content_type $www_example_com
Francis Daly Wrote:
> In this case, it looks to me that you can probably "return" rather
> than
> "rewrite", since everything should probably be a http redirect.
> non-Mediawiki URL
> [...] Except I would have the config be not a lot more than
>
> location = /wiki/index.php { return 301
> http
Hello.
I'm diverting traffic from an retired MediaWiki site to an active static
site. I'm somewhat confused with the process of `rewrite`-ing old URLs with
a query string to standard URLs *without* a query string on the static site.
For clarity, I do not need or want query strings on the new site.
25 matches
Mail list logo
