Explore >> Select a destination
|
You are here 
|
robertnealan.com | ||
| | | | |
www.hallada.net
|
|
| | | | | I've been meaning to add a commenting system to this blog for a while, but I couldn't think of a good way to do it. I implemented my own commenting system on my old Django personal site. While I enjoyed working on it at the time, it was a lot of work, especially to fight the spam. Now that my blog is hosted statically on Github's servers, I have no way to host something dynamic like comments. | |
| | | | |
eamonnsullivan.co.uk
|
|
| | | | | One huge and welcome change in the last decade or so for Web development is that secure connections are ubiquitous. Free certificates are available and most hosting providers make it very easy to obtain, use and renew the certificates automatically. This site, for example, runs on Amazon Web Services and enabling https took not much more effort than ticking a few checkboxes.Browsers, like Chrome, Firefox and Safari, have also played their part, by gently steering users toward secure connections, warning about sending sensitive information over plain text and switching to https automatically, when available. | |
| | | | |
blog.orhun.dev
|
|
| | | | | FOSS ? Linux ? Programming | |
| | | | |
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... | ||
