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

IT_man

以下是gist.github.com支援reverse proxied APIs的範例:
1 b$ R- S3 a0 H+ I
! M7 c, U1 m3 K) w8 N( C* x
' R5 q/ u5 I0 k0 t% q; |) y$ k

# CORS header support
#
# One way to use this is by placing it into a file called "cors_support"
# under your Nginx configuration directory and placing the following
6 v1 h7 M$ v! p6 b* h0 f. S( ^# i% ~# statement inside your **location** block(s):
, k3 O& A0 K+ F6 M9 E) t  H#
+ T  H  y9 e+ r! a5 o! i% Y9 A1 I2 }8 |#   include cors_support;
#
% p; _- e% F( q; p# G# 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.
2 b- W) D4 S5 w# X+ C#
# a* Q( j6 x. k. K4 u# x9 i* q% b# For more information on CORS, please see: http://enable-cors.org/
6 _7 q  G# Y7 c" \7 c: M# Forked from this Gist: https://gist.github.com/michiel/1064640
#

set $cors '';
if ($http_origin ~ '^https?://(localhost|www\.yourdomain\.com|www\.yourotherdomain\.com)$') {
        set $cors 'true';
}

$ V! Z4 N8 W" s2 Gif ($cors = 'true') {
        add_header 'Access-Control-Allow-Origin' "$http_origin" always;
. c% K* w& ]8 O6 Z$ a0 a        add_header 'Access-Control-Allow-Credentials' 'true' always;
+ @4 c/ t7 B$ |3 Z        add_header 'Access-Control-Allow-Methods' 'GET, POST, PUT, DELETE, OPTIONS' always;
. H$ U0 N+ A. N1 n1 Q. v: n        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
  s  G- A+ I; j8 F2 t  [        #add_header 'Access-Control-Expose-Headers' 'Authorization' always;
}

if ($request_method = 'OPTIONS') {
3 B' w! ?6 t# J7 v6 v4 U4 W        # Tell client that this pre-flight info is valid for 20 days
$ l8 u% @# Q" m: [* C& N        add_header 'Access-Control-Max-Age' 1728000;
        add_header 'Content-Type' 'text/plain charset=UTF-8';
" X$ W9 T5 M: T; t! r        add_header 'Content-Length' 0;
        return 204;
}

https://gist.github.com/Stanback/7145487#file-nginx-conf 的討論範例:
, u- l9 t; c& D6 m; A" A

if ( $request_method !~ ^(GET|POST|HEAD|OPTIONS|PUT|PATCH|DELETE)$ ) {     return 444;
; _' z. o! g1 X5 B. c, _# g4 [& B5 n}
set $origin $http_origin;
1 C  v" r$ X0 r  {if ($origin !~ '^https?://(subdom1|subdom2)\.yourdom\.zone$') {
     set $origin 'https://default.yourdom.zone';
0 ~6 h' C. U7 C/ C}
  X+ v2 i1 U9 j5 a) Jif ($request_method = 'OPTIONS') {
: t3 k; r' N$ Q1 q' G) T     add_header 'Access-Control-Allow-Origin' "$origin" always;
     add_header 'Access-Control-Allow-Methods' 'GET, POST, PATCH, PUT, DELETE, OPTIONS' always;
     add_header 'Access-Control-Allow-Headers' 'Content-Type, Accept, Authorization' always;
6 k' B* Y% Y6 l4 I     add_header 'Access-Control-Allow-Credentials' 'true' always;
# w, ~; k$ s- _3 b* [- K. k     add_header Access-Control-Max-Age 1728000;   #20 days   
& [; i& Y/ U; L5 l$ e6 G3 D6 Z  B7 v* N, ^     add_header Content-Type 'text/plain charset=UTF-8';
     add_header Content-Length 0;
     return 204;
- `- n" }' L: n}
if ($request_method ~ '(GET|POST|PATCH|PUT|DELETE)') {
     add_header Access-Control-Allow-Origin "$origin" always;
! b4 Y: v, ?& d1 I     add_header Access-Control-Allow-Methods 'GET, POST, PATCH, PUT, DELETE, OPTIONS' always;
* r9 F$ _( E) z5 M5 y9 O     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/
#
# Slightly tighter CORS config for nginx
5 b' [" T5 \3 k* B' N8 V, x, A#
3 N0 h+ L& X' t8 Z# A modification of https://gist.github.com/1064640/ to include a white-list of URLs
; w5 w2 H9 t+ P3 T0 W. [) w$ I4 P1 ?9 q#
# Despite the W3C guidance suggesting that a list of origins can be passed as part of
# ]$ h; W) B7 d" ~+ s% C# Access-Control-Allow-Origin headers, several browsers (well, at least Firefox)
# don't seem to play nicely with this.
#
# To avoid the use of 'Access-Control-Allow-Origin: *', use a simple-ish whitelisting
% A" Q3 A4 M) ]6 O+ Z' C, c) @# method to control access instead.
#
# NB: This relies on the use of the 'Origin' HTTP Header.

5 N3 a) Y% @0 c& x4 C2 qlocation / {

% _, I0 L, W' H& H( T/ Y% t; M7 V" C    if ($http_origin ~* (^https?://([^/]+\.)*(domainone|domaintwo)\.com$)) {
5 v; I, C& F& N) H/ P        set $cors "true";
  ^, U7 [" ^+ k% H    }

    # Nginx doesn't support nested If statements. This is where things get slightly nasty.
    # Determine the HTTP request method used
    if ($request_method = 'OPTIONS') {
8 g3 S" H& n# R        set $cors "${cors}options";
0 U. G$ [1 [' C8 d+ K    }
8 u( P& F" Z; F) |" R$ G- K7 L% y    if ($request_method = 'GET') {
        set $cors "${cors}get";
1 \- b' i+ c1 z    }
* t4 l+ w7 @# o% V5 K4 U5 w, n    if ($request_method = 'POST') {
" b7 c  W; X% n+ B, J# F        set $cors "${cors}post";
# I) a9 N* z( \. n    }
. O# W& `5 d) m2 [( d
    if ($cors = "true") {
, h7 g* i* E; o5 P( ]        # Catch all incase there's a request method we're not dealing with properly
        add_header 'Access-Control-Allow-Origin' "$http_origin";
! @2 Q1 U4 w! P, p: f* t    }
2 N( E4 p! F& L3 y
    if ($cors = "trueget") {
        add_header 'Access-Control-Allow-Origin' "$http_origin";
$ ^  \' _: ^. V4 p) D2 X        add_header 'Access-Control-Allow-Credentials' 'true';
; ^8 |1 W: \5 U        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
        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";
9 {- u0 d6 {- i
        #
2 \7 G7 y2 Z* x& f/ O$ `6 u        # Om nom nom cookies
3 B/ {6 Q$ A1 [+ }        #
: {) F# T2 U% Q  v8 z        add_header 'Access-Control-Allow-Credentials' 'true';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';

        #
        # 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';
& S1 N$ K+ c4 g* E1 g7 Z: M
( x& ]% j; U) m# o  X# }( U  C7 j        #
        # Tell client that this pre-flight info is valid for 20 days
        #
        add_header 'Access-Control-Max-Age' 1728000;
        add_header 'Content-Type' 'text/plain charset=UTF-8';
        add_header 'Content-Length' 0;
        return 204;
  k1 B+ h/ V0 n! W+ \: x' ?3 l    }
9 J% ^1 A4 G8 P5 N+ Z
  O) E( B$ Z; `% }    if ($cors = "truepost") {
        add_header 'Access-Control-Allow-Origin' "$http_origin";
+ B3 S& n8 B2 ?' Y/ S7 X        add_header 'Access-Control-Allow-Credentials' 'true';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
4 x$ w- m- o! l9 k4 o4 @9 m! `        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
6 K6 C( |8 w4 m- z    }
. o; n# I! j: J4 \
! L7 [' K1 b1 s4 l& u0 \9 x}

0 x( @3 B" o6 H9 t
5 g) ]; e# G" o7 I, p6 K+ }