• ​github:perusio/nginx_ensite nginx_ensite and nginx_dissite for quick virtual host enabling and disabling

• ​nginx: SNI拡張を使ってVirtualHostでTLSを設定 | bluegold

• ​Blog: nginxとuwsgiを使ってTracをホストしよう – 俺が文献だ

forward proxy

• ​YellowStore: (Nginx)フォワードプロキシを構築する

• ​https and nginx as forward proxy
  • nginxではhttpsをforward proxyとして処理することは出来ない

    192.168.X.Y - - [30/Dec/2012:17:27:16 +0900] "CONNECT lab.mitty.jp:443 HTTP/1.1" 400 173 "-" "-"
    

  • http forward proxyとしては正常に動作する
• forawrd proxy portをSSL(443)で稼働しても不可
  • この場合、http proxyとしても動作しなくなる

    192.168.X.Y - - [30/Dec/2012:17:35:36 +0900] "GET http://lab.mitty.jp/ HTTP/1.1" 400 271 "-" "Mozilla/5.0 (Windows NT 6.1; WOW64; rv:17.0) Gecko/17.0 Firefox/17.0"
    

logging to pipe(7)

• ​#73 (Support logging to external process (pipe) in HttpLogModule) – nginx

  No, thanks. If you really want logging to an external process - try using mkfifo(1), but please keep in mind that this will lead to service interruption if your logging process won't be able to cope with load. I would recommend logging to a normal file and using "tail -F /path/to/log | script" instead if you need some log processing.

• ​ntaka blog : nginxでcronologを使う - livedoor Blog（ブログ）
• ​What happens to nginx when I use named pipes as log file and remove and recreate the pipe? - Stack Overflow

• crontabで23:59にmv access_log access_log.`date`、00:00にkill -USR1 `cat /var/run/nginx.pid`とした方がよさそう
  • 00:00にmvすると次の日の日付でファイル名が決まってしまう