/explore
|
You are here |
www.thebacklog.net | ||
| | | | |
blog.erethon.com
|
|
| | | | | ||
| | | | |
pvanhoof.be
|
|
| | | | | ||
| | | | |
jfoucher.com
Do you know Mailtrap.io? Well this is the same, but without sending (possibly) confidential data to a third party |
|
| | | | | ||
| | | | |
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 upstream web requests. |
|
| | | |||