Kirill Berezin Enelar

Nginx TLS SNI routing, based on subdomain pattern

Nginx can be configured to route to a backend, based on the server's domain name, which is included in the SSL/TLS handshake (Server Name Indication, SNI).
This works for http upstream servers, but also for other protocols, that can be secured with TLS.

prerequisites

at least nginx 1.15.9 to use variables in ssl_certificate and ssl_certificate_key.
check nginx -V for the following:
```
...
TLS SNI support enabled
```

	<!DOCTYPE HTML>
	<html>
	<head>
	<title>Enable And Disable jQuery Event Handlers</title>
	<style type="text/css">

	#modal {
	background-color: #FAFAFA ;
	border: 1px solid #C0C0C0 ;
	display: none ;

	#!/usr/bin/env python2.7

	from __future__ import print_function
	import sys
	import os.path
	import re
	import shutil
	from glob import glob
	from HTMLParser import HTMLParser
	from subprocess import check_output, check_call, Popen, CalledProcessError, PIPE

	# Service Interruption Debrief

	## Brief Executive Summary

	EXECUTIVE SUMMARY HERE

	*On Call during outage*:

	*Time outage started*:

	#!/usr/bin/env bash

	# This function lets you easily create series of commands into a single call
	# It will print each successive command, run it and, as long as it returned
	# with code 0, continue to the next step.
	# If any step fails, it will stop and let you pick it back up after you fix the
	# issues.
	#
	# Example of script using this function:
	# !/usr/bin/env bash