|
You are here |
blog.heckel.io | ||
| | | | |
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... | |
| | | | |
pixelesque.net
|
|
| | | | | HTTPS TLS Webserver support with S2N | |
| | | | |
blog.yadutaf.fr
|
|
| | | | | ||
| | | | |
blog.zespre.com
|
|
| | | Its always recommended to view web pages through HTTPS connections, even its just a static HTML page. So, as a content provider, its my duty to host websites with HTTPS. To enable HTTPS on the web server like Apache or Nginx, valid certificates are required. In my case, I have bought and configured a domain name on Gandi.net for my home cluster. Its better to have different certificates for each service than having a single wildcard certificate for all the services due to security concerns. However, I st... | ||