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

IT_man

以下是gist.github.com支援reverse proxied APIs的範例:
0 d2 W+ E) T. J" @3 t( R

- y% Y, r0 g& X) I' V: R* X

# CORS header support
#
! ]# P* T9 @9 w! {% V/ |# One way to use this is by placing it into a file called "cors_support"
% ]6 [$ F. I# h+ @9 G' a# under your Nginx configuration directory and placing the following
# statement inside your **location** block(s):
#
#   include cors_support;
#
# 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.
#
3 |! S: B" f: M( C) j3 y# For more information on CORS, please see: http://enable-cors.org/
# Forked from this Gist: https://gist.github.com/michiel/1064640
  s( E& V) O% L$ U3 Q#

set $cors '';
if ($http_origin ~ '^https?://(localhost|www\.yourdomain\.com|www\.yourotherdomain\.com)$') {
        set $cors 'true';
. b; K+ x! H/ K6 n# K}
9 P$ Q. N1 F9 ?" n& l( ^
) P' ^; B) y4 D6 H( Uif ($cors = 'true') {
) Q4 x6 l# o5 }+ P) F% @! z: f. F: h! V        add_header 'Access-Control-Allow-Origin' "$http_origin" always;
        add_header 'Access-Control-Allow-Credentials' 'true' always;
7 K: ?' ?! M. ?# l, F        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
% X0 B7 k+ A9 V5 C% x        #add_header 'Access-Control-Expose-Headers' 'Authorization' always;
# `1 X5 z. |2 n2 N9 q$ p7 \) {+ ~1 H}
5 t! ^& @! k9 M/ Q. f4 K! d2 O1 x- c
" ~9 }' ^: I' i3 l' e" o" b2 ~$ p6 @if ($request_method = 'OPTIONS') {
$ B- s0 d, J/ \+ V" r        # Tell client that this pre-flight info is valid for 20 days
        add_header 'Access-Control-Max-Age' 1728000;
6 s: i8 L3 U- o# z        add_header 'Content-Type' 'text/plain charset=UTF-8';
        add_header 'Content-Length' 0;
        return 204;
: b& v  G0 L& \: R2 J}

https://gist.github.com/Stanback/7145487#file-nginx-conf 的討論範例:
3 i- p8 E$ g# T  d& v" k: _

if ( $request_method !~ ^(GET|POST|HEAD|OPTIONS|PUT|PATCH|DELETE)$ ) {     return 444;
}
set $origin $http_origin;
* ~+ C' b& N) ]+ g$ rif ($origin !~ '^https?://(subdom1|subdom2)\.yourdom\.zone$') {
     set $origin 'https://default.yourdom.zone';
}
+ w: h, ~7 D# A1 B7 yif ($request_method = 'OPTIONS') {
     add_header 'Access-Control-Allow-Origin' "$origin" always;
& n2 Z$ P1 h& A0 H1 j* W     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;
1 w2 E' D' ?. `( W     add_header Access-Control-Max-Age 1728000;   #20 days   
     add_header Content-Type 'text/plain charset=UTF-8';
# M/ g9 C* I8 n8 z1 j     add_header Content-Length 0;
     return 204;
}
if ($request_method ~ '(GET|POST|PATCH|PUT|DELETE)') {
; j5 b0 n0 W3 l5 T- z9 D' i     add_header Access-Control-Allow-Origin "$origin" always;
# ~) F# N8 N2 _( a     add_header Access-Control-Allow-Methods 'GET, POST, PATCH, PUT, DELETE, OPTIONS' always;
     add_header Access-Control-Allow-Headers 'Content-Type, Accept, Authorization' always;
; y$ Q. M4 W) J9 P" j6 t& p+ ^# V% T     add_header Access-Control-Allow-Credentials true always;
' U* h7 L" r" ?}

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

# based on https://gist.github.com/4165271/
$ I8 d! L  d9 u#
: T- L8 i) |1 b; O: ?# Slightly tighter CORS config for nginx
#
# A modification of https://gist.github.com/1064640/ to include a white-list of URLs
% r( v  S7 `. W1 p, [6 ?; Z#
' V1 r( T- j- R5 q6 f4 ]# 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)
/ l7 P+ @: Y: O' i  o4 n# don't seem to play nicely with this.
' z$ c9 M% @7 ?! P#
# To avoid the use of 'Access-Control-Allow-Origin: *', use a simple-ish whitelisting
! h& W2 _. @  A% ]# method to control access instead.
( C# U& x6 n, Y& ^3 Q0 j$ {#
# NB: This relies on the use of the 'Origin' HTTP Header.
4 V+ Y' y7 l# `8 T
  P# x* ?; S- A" ~; m" Clocation / {

- u9 `* \0 ], r) ~    if ($http_origin ~* (^https?://([^/]+\.)*(domainone|domaintwo)\.com$)) {
* q4 B, Y/ T' Y* X        set $cors "true";
    }
9 I9 |2 s/ f8 ?
    # Nginx doesn't support nested If statements. This is where things get slightly nasty.
% G( _" I' J& Z    # Determine the HTTP request method used
    if ($request_method = 'OPTIONS') {
        set $cors "${cors}options";
  ?1 a& O( {* j& G7 T    }
! Z' Y- P: T9 u& A+ ^0 c  h. u    if ($request_method = 'GET') {
  a5 q; o9 @1 C4 Z) a        set $cors "${cors}get";
1 l6 M& Q  q+ v( X9 D) t    }
+ \  {$ A( s* T+ T. L7 Z; @' n    if ($request_method = 'POST') {
        set $cors "${cors}post";
    }

4 q* q4 `" T1 ]+ Q5 {) v    if ($cors = "true") {
        # Catch all incase there's a request method we're not dealing with properly
  u; s6 b* T# Z3 q        add_header 'Access-Control-Allow-Origin' "$http_origin";
    }

, {6 A$ u1 ~8 H# D    if ($cors = "trueget") {
9 [8 O& t) |6 X9 h        add_header 'Access-Control-Allow-Origin' "$http_origin";
        add_header 'Access-Control-Allow-Credentials' 'true';
# |4 l" R& x8 p* e        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
/ E. w3 k; _0 T, C3 b. B. W        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";

        #
        # Om nom nom cookies
        #
6 d, s% y1 M' ~9 Q        add_header 'Access-Control-Allow-Credentials' 'true';
9 d9 [% V" u+ ^( o6 E" F        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
* H, i2 v! |" \, j
        #
7 Y% u' q* P& I. T7 U- B  G        # Custom headers and headers various browsers *should* be OK with but aren't
        #
        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
/ a' y2 w( O& N3 J1 R
( I0 E* e  x: E8 K% A+ M        #
) X7 O) C0 ?  T7 M2 i/ a8 e$ \+ t        # Tell client that this pre-flight info is valid for 20 days
        #
& y$ _, V. |0 C- a" o. J- U6 G9 P        add_header 'Access-Control-Max-Age' 1728000;
# h/ D' {6 E1 O; m  ^2 l        add_header 'Content-Type' 'text/plain charset=UTF-8';
        add_header 'Content-Length' 0;
0 z' Z4 ?; t; _4 F" e* A        return 204;
& Y8 b0 a/ Y8 o: T    }
, \( {( J  `, r2 b: w
    if ($cors = "truepost") {
, }  V" t) |1 X8 l3 B* {        add_header 'Access-Control-Allow-Origin' "$http_origin";
0 ^% s9 u4 Y0 |4 C: N        add_header 'Access-Control-Allow-Credentials' 'true';
+ U7 g0 D) X1 L2 t1 i( s5 u        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
5 A4 R4 R7 y$ B! w% Y: e4 f1 n        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
2 c5 w" _# l! V: J( E" D    }

) q1 P, P, R# _4 z( i; d) X' x; a+ [}

3 j1 K, r; o8 d/ {