Explore >> Select a destination
|
You are here 
|
www.janhouse.lv | ||
| | | | |
joshuarogers.net
|
|
| | | | | Just over a year ago we went over how to setup a reverse proxy that would require our users to authenticate. In our original proxy article, we generated some NGinx configuration that looked a bit like... location / { proxy_pass http://jira; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; } And it worked. And everyone was happy. Until the day the request came in that NGinx should add a fixed set of credentials to all upstre... | |
| | | | |
daenney.github.io
|
|
| | | | | I blog about what catches my fancy | |
| | | | |
niemczuk.tech
|
|
| | | | | ||
| | | | |
hjr265.me
|
|
| | | HTTP3 is here. Well, almost. If you are using NGINX, you can update to the mainline version and start using HTTP3 today experimentally. Installing NGINX Mainline As of writing this blog post, NGINX v1.24 is the latest stable version. But, HTTP3 is available in v1.25. On Ubuntu/Debian-esque servers, the easiest way to install the mainline NGINX version is to use NGINX's official repository. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 apt install curl gnupg2 ca-certificates lsb-release debian-archive-keyring # Import the official NGINX signing key. | ||
