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

IT_man

以下是gist.github.com支援reverse proxied APIs的範例:
$ K# o- K! H* ^5 L0 @) v
8 W0 n2 H6 x5 F+ p5 |3 G
- V& p3 d4 d6 a- s5 R; \0 H* e# o, i3 A

# CORS header support
#
# One way to use this is by placing it into a file called "cors_support"
( U. A4 h$ y  Z# U; I& a# {8 m# under your Nginx configuration directory and placing the following
( q. Y; Z6 x7 i; P4 K' o8 q/ U# statement inside your **location** block(s):
#
#   include cors_support;
#
7 K; C* I, N6 B* _# As of Nginx 1.7.5, add_header supports an "always" parameter which
0 ~! t" V3 {" ]) s5 b# allows CORS to work if the backend returns 4xx or 5xx status code.
#
# For more information on CORS, please see: http://enable-cors.org/
# Forked from this Gist: https://gist.github.com/michiel/1064640
+ A2 V2 ~( i" A#

set $cors '';
+ Z: L9 w% E& `# n+ B4 iif ($http_origin ~ '^https?://(localhost|www\.yourdomain\.com|www\.yourotherdomain\.com)$') {
2 U: R1 ?. S- p! B5 h        set $cors 'true';
; M0 \; {4 U2 L& z8 _6 g" C: D}

  o  k/ n: G9 n. c4 O, O- tif ($cors = 'true') {
0 ~5 n% l# P* e- l        add_header 'Access-Control-Allow-Origin' "$http_origin" always;
        add_header 'Access-Control-Allow-Credentials' 'true' always;
        add_header 'Access-Control-Allow-Methods' 'GET, POST, PUT, DELETE, OPTIONS' always;
: z: o$ o" |: F6 A) n& o/ @        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;
9 X) o' W1 e% O- n4 n1 A        # required to be able to read Authorization header in frontend
        #add_header 'Access-Control-Expose-Headers' 'Authorization' always;
7 D9 q% C2 g$ W/ ?( j}
: Z/ }1 C# d! N/ e6 _% V7 \  L
) b2 O% I3 L/ c& h+ ^2 Eif ($request_method = 'OPTIONS') {
        # Tell client that this pre-flight info is valid for 20 days
        add_header 'Access-Control-Max-Age' 1728000;
! t. z6 p) \) J( x3 d) A- C        add_header 'Content-Type' 'text/plain charset=UTF-8';
# n) t$ Y" |- K, I+ R( z' e' E        add_header 'Content-Length' 0;
        return 204;
}

https://gist.github.com/Stanback/7145487#file-nginx-conf 的討論範例:
2 a0 ?" b- y/ b; H) T

if ( $request_method !~ ^(GET|POST|HEAD|OPTIONS|PUT|PATCH|DELETE)$ ) {     return 444;
}
+ |" H  Q- K" y) I. K8 s7 Z2 e& Jset $origin $http_origin;
2 k1 w6 |4 Y% _& Hif ($origin !~ '^https?://(subdom1|subdom2)\.yourdom\.zone$') {
     set $origin 'https://default.yourdom.zone';
' k# o# z* W3 s}
if ($request_method = 'OPTIONS') {
     add_header 'Access-Control-Allow-Origin' "$origin" always;
     add_header 'Access-Control-Allow-Methods' 'GET, POST, PATCH, PUT, DELETE, OPTIONS' always;
3 F0 v5 a& D% ]     add_header 'Access-Control-Allow-Headers' 'Content-Type, Accept, Authorization' always;
0 u1 d/ t7 H3 O" S     add_header 'Access-Control-Allow-Credentials' 'true' always;
     add_header Access-Control-Max-Age 1728000;   #20 days   
1 T5 t5 Y; s( J( v" P8 |" F     add_header Content-Type 'text/plain charset=UTF-8';
     add_header Content-Length 0;
2 S" I- X1 O. @     return 204;
, y# E! [( F- `7 M4 V}
if ($request_method ~ '(GET|POST|PATCH|PUT|DELETE)') {
     add_header Access-Control-Allow-Origin "$origin" always;
* F/ X& A, @' _3 k2 Q     add_header Access-Control-Allow-Methods 'GET, POST, PATCH, PUT, DELETE, OPTIONS' always;
     add_header Access-Control-Allow-Headers 'Content-Type, Accept, Authorization' always;
     add_header Access-Control-Allow-Credentials true always;
}

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

# based on https://gist.github.com/4165271/
3 b3 }7 p0 b, ~% A) Y#
$ |, [: B7 ]4 f- ~/ y# Slightly tighter CORS config for nginx
7 }, l0 Z# I3 N  [$ |#
$ B# w- t0 a) `0 q# A modification of https://gist.github.com/1064640/ to include a white-list of URLs
#
# Despite the W3C guidance suggesting that a list of origins can be passed as part of
# Access-Control-Allow-Origin headers, several browsers (well, at least Firefox)
% I/ f# I$ u$ u# don't seem to play nicely with this.
8 t$ q3 M1 D3 U4 k1 x; v#
# To avoid the use of 'Access-Control-Allow-Origin: *', use a simple-ish whitelisting
# method to control access instead.
' \4 Q) M  B1 J#
8 x9 M; x4 G7 i" A6 e  O4 q# NB: This relies on the use of the 'Origin' HTTP Header.

location / {
( G$ z/ r7 e$ B# n8 h3 p
, \; H' d2 S$ X% ~3 H    if ($http_origin ~* (^https?://([^/]+\.)*(domainone|domaintwo)\.com$)) {
        set $cors "true";
7 D$ J$ J1 `; e* r- Z& q    }

% C" m$ E' V% r& {    # Nginx doesn't support nested If statements. This is where things get slightly nasty.
4 y. |, s6 k7 H6 o( T    # Determine the HTTP request method used
    if ($request_method = 'OPTIONS') {
6 d6 z( `/ |7 G4 u# L; m        set $cors "${cors}options";
    }
) ~9 s( r) y2 y: \    if ($request_method = 'GET') {
        set $cors "${cors}get";
/ }1 L' S: D7 E; k6 Y+ V/ F9 J+ i: t    }
    if ($request_method = 'POST') {
        set $cors "${cors}post";
    }
* E) |# O' A- p, V) N
    if ($cors = "true") {
  E0 q& s2 w9 x8 @, I1 k        # Catch all incase there's a request method we're not dealing with properly
4 j7 }5 i. A- d2 i5 P: Q        add_header 'Access-Control-Allow-Origin' "$http_origin";
    }

    if ($cors = "trueget") {
/ a# G0 Y4 s1 U! j( |+ y/ ?4 k        add_header 'Access-Control-Allow-Origin' "$http_origin";
) C1 k% b" D" l9 X        add_header 'Access-Control-Allow-Credentials' 'true';
% |2 F+ j, c! T/ {; c        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
9 T$ c8 m! V% r1 B        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";
* v' K2 i8 c/ t# v, z, v
        #
        # Om nom nom cookies
9 J% [: L5 t' z! J9 w9 P        #
        add_header 'Access-Control-Allow-Credentials' 'true';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
1 q/ U  d* q$ x, ?
# A+ a. `+ _/ m        #
/ W! w( v+ ^) \0 y9 l' g$ c        # Custom headers and headers various browsers *should* be OK with but aren't
        #
, y+ }6 V" \/ T# X        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
; [9 n* I3 l" ^0 d) `  Q
        #
        # Tell client that this pre-flight info is valid for 20 days
7 g6 P# D# w- O4 \4 R/ t: {        #
        add_header 'Access-Control-Max-Age' 1728000;
9 N' C4 Q1 v5 c2 C; [9 l        add_header 'Content-Type' 'text/plain charset=UTF-8';
        add_header 'Content-Length' 0;
        return 204;
# q  n& N5 ?6 t: g# }6 i8 s8 x    }
, Q1 R' W& A9 F4 y
8 ^5 S. n! m" D  ]7 }    if ($cors = "truepost") {
" G" A* x( _0 \+ d  o2 |* K/ C        add_header 'Access-Control-Allow-Origin' "$http_origin";
, G+ ~9 O& _1 l9 s9 C0 u        add_header 'Access-Control-Allow-Credentials' 'true';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
4 H5 M5 g6 z$ Q5 e; l( f0 X9 K        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
    }
' t& x9 J8 m* v
}