Custom Query (2311 matches)

We have

proxy_cache_use_stale updating ...

in our proxy configurations, and on some paths, upstream is sending

cache-control: no-cache, no-store, must-revalidate
pragma: no-cache
expires: 0

in a 302 response.

It seems that nginx is caching this sometimes, because some clients are receiving 404 and all of those requests are

cache_status=UPDATING

.

It happens for 1 percent of clients and whenever I try to reproduce this I get

cache_status=EXPIRED

, so I'm not sure how to go further with this.

Hello there!

Ubuntu 23.10 with code name mantic was released 12.10.2023. There is only a stable version 1.24.0 in the basic OS repos:

# apt list nginx*
Listing... Done
nginx-common/mantic 1.24.0-1ubuntu1 all
nginx-confgen/mantic 2.1-1 amd64
nginx-core/mantic 1.24.0-1ubuntu1 all
nginx-dev/mantic 1.24.0-1ubuntu1 all
nginx-doc/mantic 1.24.0-1ubuntu1 all
nginx-extras/mantic 1.24.0-1ubuntu1 amd64
nginx-full/mantic 1.24.0-1ubuntu1 all
nginx-light/mantic 1.24.0-1ubuntu1 all
nginx/mantic 1.24.0-1ubuntu1 amd64

Im trying to use as usual nginx packages repo for Linux nginx.org according to ​https://nginx.org/en/linux_packages.html#Ubuntu

When trying to install a package:

# apt update
...
Ign:4 http://nginx.org/packages/ubuntu mantic InRelease
Err:5 http://nginx.org/packages/ubuntu mantic Release
...
Reading package lists... Done
E: The repository 'http://nginx.org/packages/ubuntu mantic Release' does not have a Release file.
N: Updating from such a repository can't be done securely, and is therefore disabled by default.

Then I used direct links to find out if the package was in the repo:

• stable: ​https://nginx.org/packages/ubuntu/pool/nginx/n/nginx/
• mainline: ​https://nginx.org/packages/mainline/ubuntu/pool/nginx/n/nginx/

There are no packages with mantiс code in the *.deb filenames on repo.

It is necessary to build stable and mainline versions of packages and place them in the nginx.org repo.

Thank you)

PS: a few technical details:

# uname -a
Linux vmx117 6.5.0-10-generic #10-Ubuntu SMP PREEMPT_DYNAMIC Fri Oct 13 13:49:38 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

# dpkg --list 'linux-image*'
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name                                  Version      Architecture Description
+++-=====================================-============-============-=================================
un  linux-image                           <none>       <none>       (no description available)
ii  linux-image-6.5.0-10-generic          6.5.0-10.10  amd64        Signed kernel image generic
ii  linux-image-6.5.0-9-generic           6.5.0-9.9    amd64        Signed kernel image generic
ii  linux-image-generic                   6.5.0.10.12  amd64        Generic Linux kernel image
un  linux-image-unsigned-6.5.0-10-generic <none>       <none>       (no description available)
un  linux-image-unsigned-6.5.0-9-generic  <none>       <none>       (no description available)

# lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description:    Ubuntu 23.10
Release:        23.10
Codename:       mantic

# cat /etc/os-release
PRETTY_NAME="Ubuntu 23.10"
NAME="Ubuntu"
VERSION_ID="23.10"
VERSION="23.10 (Mantic Minotaur)"
VERSION_CODENAME=mantic
ID=ubuntu

Using: │app.kubernetes.io/name: rke2-ingress-nginx │app.kubernetes.io/version: 1.6.4 │helm.sh/chart: rke2-ingress-nginx-4.5.201 Having an ingress with: │ rules: │ - http: │ paths: │ - backend: │ service: │ name: powerflex-status-ui │ port: │ number: 80 │ path: / │ pathType: Exact

When calling:

curl -k -H 'Cache-Control: no-cache, no-store' -I ​https://100.68.80.54/

HTTP/2 404

It worked with an older version. We have a workaround, adding $ to the expression.

│ rules: │ - http: │ paths: │ - backend: │ service: │ name: powerflex-status-ui │ port: │ number: 80 │ path: /$ │ pathType: Exact

That one seems identical but it works - getting http 200