Re: Is there a conflict between Debian Bullseye and nginx?

On Fri, 2022-12-16 at 15:59 +, Francis Daly wrote: > On Fri, Dec 16, 2022 at 04:27:15PM +0800, Mike Lieberman wrote: > > Hi there, > > You have configured your nginx to listen on port 80 on all IP addresses. > > You have configured your apache to listen on port 8

Is there a conflict between Debian Bullseye and nginx?

-xe" for details. failed! root@www:/home/mike# systemctl status apache2.service ● apache2.service - The Apache HTTP Server Loaded: loaded (/lib/systemd/system/apache2.service; enabled; vendor preset: enabled) Active: failed (Result: exit-code) since Fri 2022-12-16 15:57:04 PS

how can I cache upstream by mime type in nginx

hi there My front end is nginx using reverse proxy work with my backend, I was trying to cache images files only, but it seems doesn't work at all, the *$no_cache* always output default value "proxy", which should be "0" when I visit image files here it is my config map $upstream_http_content_ty

noob needs help with alias locations and php

eneath the document_root. Example of places I want to go: non-root targets: as: /home/mike/Movies/index.html/movies/index.html200 /home/mike/Movies/index.php /movies/index.php "File not found." /home/mike/Movies/1/index.html /movies/1/index.html 404 /home/mik

1.4.1 SPDY error FIXME: chain too big in spdy filter

Hi, Running 1.4.1 and using SPDY and SSL extensively (exclusively, actually). Seeing a ton (thousands) of errors in the error log, similar to: 2013/05/29 00:22:53 [alert] 25981#0: *8781732 FIXME: chain too big in spdy filter: 25516336 while sending to client, client: x.x.x.x, server:

Nginx connection close module

ou in advance, *Mike.* ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listinfo/nginx