Re: Debugging `try_files` with 404 as a last resort

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

Re: Debugging `try_files` with 404 as a last resort

On Tue, Nov 13, 2018 at 05:23:41PM -0500, petecooper wrote: Hi there, > 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) D

Debugging `try_files` with 404 as a last resort

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)

NGINX 2018 Training Survey

Hi, At NGINX we are always trying to improve our high-performing, lightweight technology. A big part of that is our training program ( https://university.nginx.com), designed to help NGINX users build skills for both basic and advanced uses of NGINX

Re: Make ngx_http_v2_push_resource api public

Hello! On Mon, Nov 12, 2018 at 10:29:50PM -0500, Cubic wrote: > I am intend to write an Nginx module which support downstream message push > through http2 protocol. > > The main process is as below. > 1. Client connect to Nginx and use http2 protocol to send a long polling > request stream. > 2.