Posts

A reverse proxy is a server that sits between internal applications and external clients, forwarding client requests to the appropriate server. While many common applications, such as Node.js, are able to function as servers on their own, NGINX has a number of advanced load balancing, security, and acceleration features that most specialized applications lack. Using NGINX as a reverse proxy enables you to add these features to any application. Basic Configuration for an NGINX Reverse Proxy server_name example.com; ...

This tutorial will show you how to redirect a www URL to non-www, e.g. www.example.com to example.com, with Nginx. We will also show you how to redirect in the other direction, from a non-www URL to www. Configure DNS Records In order to set up the desired redirect, www.example.com to example.com or vice versa, you must have an A record for each name. Option 1: Redirect www to non-www Option 2: Redirect non-www to www

All login credentials transferred over plain HTTP can easily be sniffed by a MITM attacker, but it is not enough to encrypt the login forms. If you are visiting plain HTTP pages while logged in, your session can be hijacked, and not even two-factor authentication will protect you. To protect all info sent between your visitors – which includes you – and your web server, we will redirect all requests that are coming over plain HTTP to the HTTPS equivalent. ...

named bind server – adding multiple TXT records for the same domain

The Require provides a variety of different ways to allow or deny access to resources. In conjunction with the RequireAll, RequireAny, and RequireNone directives, these requirements may be combined in arbitrarily complex ways, to enforce whatever your access policy happens to be. example: <VirtualHost *:80> ServerName example.net Documentroot /var/www/html/ <Location /> Require ip 192.168.0.0/24 10.0.0.2 </Location>; </VirtualHost>