Nginx之CORS（Cross-Origin Resource Sharing，跨來源資源共享）來實現防止盜連多媒體資源

IT_man

以下是gist.github.com支援reverse proxied APIs的範例:
2 X( C' b: E8 U- e% N: l8 [

# CORS header support
8 y! s! A. h, k# H: @# q#
9 W4 ~2 h- Q, x* r6 {1 o# j# One way to use this is by placing it into a file called "cors_support"
( g) V- i& x6 X) H0 E$ z4 a: M% ?# under your Nginx configuration directory and placing the following
* ]+ H$ {! O1 r% l0 z( u' S# statement inside your **location** block(s):
#
#   include cors_support;
#
" O: f4 u" w1 o# As of Nginx 1.7.5, add_header supports an "always" parameter which
# allows CORS to work if the backend returns 4xx or 5xx status code.
#
# For more information on CORS, please see: http://enable-cors.org/
: ~& N1 T2 L7 z' L+ M# Forked from this Gist: https://gist.github.com/michiel/1064640
( k' m' N. ^9 H8 |) E#
+ \4 V4 o2 `  c( c2 G. T
( S+ A0 T- D1 ^1 x$ N7 pset $cors '';
4 J- i7 k# @+ uif ($http_origin ~ '^https?://(localhost|www\.yourdomain\.com|www\.yourotherdomain\.com)$') {
        set $cors 'true';
}
6 Z1 _/ y2 O  _3 k' `) `( x" Y
if ($cors = 'true') {
# A+ Y& A: t, b4 R* L        add_header 'Access-Control-Allow-Origin' "$http_origin" always;
8 \$ m% ]6 O( [/ {" M, D; X        add_header 'Access-Control-Allow-Credentials' 'true' always;
8 N+ K5 A' u7 ~% [7 L        add_header 'Access-Control-Allow-Methods' 'GET, POST, PUT, DELETE, OPTIONS' always;
        add_header 'Access-Control-Allow-Headers' 'Accept,Authorization,Cache-Control,Content-Type,DNT,If-Modified-Since,Keep-Alive,Origin,User-Agent,X-Requested-With' always;
        # required to be able to read Authorization header in frontend
        #add_header 'Access-Control-Expose-Headers' 'Authorization' always;
2 j! A& n0 O$ x% g: K7 [}

if ($request_method = 'OPTIONS') {
  g2 g) ?8 |5 s5 M; N. `  c7 ?        # Tell client that this pre-flight info is valid for 20 days
- ^. L/ B. h! k        add_header 'Access-Control-Max-Age' 1728000;
        add_header 'Content-Type' 'text/plain charset=UTF-8';
        add_header 'Content-Length' 0;
6 }! ]0 x7 D6 e7 m- T* m        return 204;
% E; H; _! o- W7 k  Q/ F}

https://gist.github.com/Stanback/7145487#file-nginx-conf 的討論範例:
7 {* V% u8 a: K" c$ u! o4 X

if ( $request_method !~ ^(GET|POST|HEAD|OPTIONS|PUT|PATCH|DELETE)$ ) {     return 444;
}
4 [, [/ {/ v/ ]2 F. xset $origin $http_origin;
if ($origin !~ '^https?://(subdom1|subdom2)\.yourdom\.zone$') {
     set $origin 'https://default.yourdom.zone';
9 \' @5 b3 Q. @8 T5 A}
if ($request_method = 'OPTIONS') {
     add_header 'Access-Control-Allow-Origin' "$origin" always;
: x; F) ?3 T5 O/ Z# \3 M5 R     add_header 'Access-Control-Allow-Methods' 'GET, POST, PATCH, PUT, DELETE, OPTIONS' always;
     add_header 'Access-Control-Allow-Headers' 'Content-Type, Accept, Authorization' always;
/ V* F/ v' A; o- h3 ~% l5 X2 q     add_header 'Access-Control-Allow-Credentials' 'true' always;
& e6 g7 Q' o7 Z     add_header Access-Control-Max-Age 1728000;   #20 days   
' y: h& |. K: m; z     add_header Content-Type 'text/plain charset=UTF-8';
     add_header Content-Length 0;
     return 204;
}
4 b% h- P) C7 V8 j  ~; S4 {0 `' f7 Fif ($request_method ~ '(GET|POST|PATCH|PUT|DELETE)') {
     add_header Access-Control-Allow-Origin "$origin" always;
     add_header Access-Control-Allow-Methods 'GET, POST, PATCH, PUT, DELETE, OPTIONS' always;
; N) p5 ?9 o3 j# j  z# P     add_header Access-Control-Allow-Headers 'Content-Type, Accept, Authorization' always;
     add_header Access-Control-Allow-Credentials true always;
/ ?5 Y$ Q" T+ X}

Access-Control-Allow-Origin Multiple Origin Domains? 的例子:

# based on https://gist.github.com/4165271/
#
# Slightly tighter CORS config for nginx
#
# A modification of https://gist.github.com/1064640/ to include a white-list of URLs
4 |  z3 `5 `: B4 m#
7 c2 A1 ]" v8 L/ g( z3 Q9 z# Despite the W3C guidance suggesting that a list of origins can be passed as part of
; u2 V9 P3 Q% d! v& S# Access-Control-Allow-Origin headers, several browsers (well, at least Firefox)
0 y4 q% L* r  g' Y! ^" R# don't seem to play nicely with this.
$ i( l& D( M5 l, R# X#
: c1 q# x- C6 O1 u# To avoid the use of 'Access-Control-Allow-Origin: *', use a simple-ish whitelisting
: b" G; X0 b% _  K# method to control access instead.
' l1 `( l7 z8 h# C#
# NB: This relies on the use of the 'Origin' HTTP Header.
7 |- `3 X2 Q* j+ B- ~) P
. q9 ?8 x% B. K/ u# a% Qlocation / {

8 V! T2 e  W$ R    if ($http_origin ~* (^https?://([^/]+\.)*(domainone|domaintwo)\.com$)) {
        set $cors "true";
    }
! t* c6 F: p( R' _6 O4 Q
1 r: B7 ?( x: x8 r  R6 B    # Nginx doesn't support nested If statements. This is where things get slightly nasty.
    # Determine the HTTP request method used
    if ($request_method = 'OPTIONS') {
  i4 V$ n$ l  E/ ?- K9 X7 M        set $cors "${cors}options";
' ]7 \3 q# W7 z' q- i* J4 P    }
    if ($request_method = 'GET') {
        set $cors "${cors}get";
1 b" ?' \1 S4 l' S    }
* n8 c; P7 u- z" S0 V$ ^7 d) ]    if ($request_method = 'POST') {
        set $cors "${cors}post";
    }

2 X3 a0 k, A5 W- P0 D    if ($cors = "true") {
$ {* x2 P6 G  H& [# A1 X# L        # Catch all incase there's a request method we're not dealing with properly
( p2 \9 v" ~; T        add_header 'Access-Control-Allow-Origin' "$http_origin";
    }

9 m& h2 F% I$ L8 P    if ($cors = "trueget") {
        add_header 'Access-Control-Allow-Origin' "$http_origin";
        add_header 'Access-Control-Allow-Credentials' 'true';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
# K7 j$ S0 k3 _3 A        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
    }

    if ($cors = "trueoptions") {
        add_header 'Access-Control-Allow-Origin' "$http_origin";

+ d, {  T7 l( n: D/ Q8 D; Y# P        #
        # Om nom nom cookies
        #
        add_header 'Access-Control-Allow-Credentials' 'true';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';

( B. B# E) H5 ]& x        #
! K) b( a+ T, v5 K2 n+ x) f% Z        # Custom headers and headers various browsers *should* be OK with but aren't
        #
5 G. B5 I3 y/ x0 N$ w% m3 Y        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';

$ E. i( J6 Y6 c$ h! z! d) @  y( A        #
% Z4 d" i. W& l  s9 |        # Tell client that this pre-flight info is valid for 20 days
' p2 p$ D& B0 _5 ]! H; `% s, Y4 U2 }        #
        add_header 'Access-Control-Max-Age' 1728000;
        add_header 'Content-Type' 'text/plain charset=UTF-8';
        add_header 'Content-Length' 0;
3 x  J5 Y" z; ^, o( E( D        return 204;
" l+ Q, L! I4 N* W. |1 l. @! w, Q    }

    if ($cors = "truepost") {
        add_header 'Access-Control-Allow-Origin' "$http_origin";
        add_header 'Access-Control-Allow-Credentials' 'true';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
5 k$ M8 [5 o5 L4 J$ R        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
1 U* Q1 v8 [1 B, E3 Y) w8 _1 @    }
. I+ K2 c' q5 Z3 u; u
}

  N, a- W* P2 g$ U6 I
- k# ^$ f9 d) a5 _, B. s$ F