Re: Strange problem with expires?

W dniu 01.03.2022 o 21:49, Grzegorz Kulewski pisze: > W dniu 01.03.2022 o 21:43, David Hu pisze: >> On 1 March 2022 20:40:48 UTC, Grzegorz Kulewski wrote: >>> Hello, >>> >>> I am using nginx 1.21.0 to serve static files for one domain and when I >>> have: >>> >>>location = / { >>>

Re: Strange problem with expires?

W dniu 01.03.2022 o 21:43, David Hu pisze: > On 1 March 2022 20:40:48 UTC, Grzegorz Kulewski wrote: >> Hello, >> >> I am using nginx 1.21.0 to serve static files for one domain and when I have: >> >>location = / { >>expires epoch; >>} >> >> e

Re: Strange problem with expires?

= is for exact matches, so unless your static file is called / - it obviously won’t match that exact location. No modifier (so no =) means it’s a prefix Get Outlook for iOS From: Grzegorz Kulewski Sent: Wednesday, March 2, 2022 4:40:48 AM

Re: Strange problem with expires?

On 1 March 2022 20:40:48 UTC, Grzegorz Kulewski wrote: >Hello, > >I am using nginx 1.21.0 to serve static files for one domain and when I have: > >location = / { >expires epoch; >} > >expire headers are not added for / but when I remove '=' t

Strange problem with expires?

Hello, I am using nginx 1.21.0 to serve static files for one domain and when I have: location = / { expires epoch; } expire headers are not added for / but when I remove '=' they are. Is this some bug or just me doing something stupid? Ca

Re: Upstream certificate validation - Servers in a server group

Hello! On Tue, Mar 01, 2022 at 09:26:23AM +, Nitsan Matsliah via nginx wrote: > Assuming I have 2 servers in an upstream server group: > > 1. Test1.server.local > 2. Test2.server.local > Each one of these servers holds their own FQDN in their > respective certificates. > Test1.server.

Upstream certificate validation - Servers in a server group

Assuming I have 2 servers in an upstream server group: 1. Test1.server.local 2. Test2.server.local Each one of these servers holds their own FQDN in their respective certificates. Test1.server.local will have test1.server.local as its subject and subject alternative name in the certificate