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

IT_man

tid=101068&以下是gist.github.com支援reverse proxied APIs的範例:

5 e& }. r" ^6 _! A$ [" ~" a7 f* G

# CORS header support
: e3 e: `2 \; d/ u8 |0 y* V#
# One way to use this is by placing it into a file called "cors_support"
# |- `0 y# z" ?1 y) |0 m/ e+ i' z# under your Nginx configuration directory and placing the following
9 x; m& m8 B1 k& N: j  b$ a# statement inside your **location** block(s):
#
#   include cors_support;
5 f* E) ^# f2 G, M1 @* i#
, P' T2 V0 a) o! q/ P# As of Nginx 1.7.5, add_header supports an "always" parameter which
% J, R* j2 i! o  y) Z, A# 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
/ Y1 |& b3 S1 W  u#

2 E/ J* T/ {& ]4 j, e, e$ iset $cors '';
' B& f' X- F: ^) Xif ($http_origin ~ '^https?://(localhost|www\.yourdomain\.com|www\.yourotherdomain\.com)$') {
8 I% p! K( c- Z% [" }        set $cors 'true';
9 ?" q9 G  V9 `$ }4 F7 A8 f}

if ($cors = 'true') {
1 G- R: s' V! [/ u) ~        add_header 'Access-Control-Allow-Origin' "$http_origin" always;
        add_header 'Access-Control-Allow-Credentials' 'true' always;
5 v6 {2 Z, e( M0 z) w        add_header 'Access-Control-Allow-Methods' 'GET, POST, PUT, DELETE, OPTIONS' always;
- \/ L+ q9 `- Y) q. C. W        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;
# w7 |; l8 T3 b7 W        # required to be able to read Authorization header in frontend
3 [$ M7 D9 ]7 U0 I        #add_header 'Access-Control-Expose-Headers' 'Authorization' always;
}
7 q: T% j+ }; z$ V& n7 L
if ($request_method = 'OPTIONS') {
        # Tell client that this pre-flight info is valid for 20 days
        add_header 'Access-Control-Max-Age' 1728000;
2 m7 V! |7 Z1 b  o; l; R        add_header 'Content-Type' 'text/plain charset=UTF-8';
        add_header 'Content-Length' 0;
! U  Q+ M- N# s  O3 I0 V2 m+ _        return 204;
}

https://gist.github.com/Stanback/7145487#file-nginx-conf 的討論範例:
$ Q9 h1 r8 k( f( h# b1 J1 Y3 [7 s

if ( $request_method !~ ^(GET|POST|HEAD|OPTIONS|PUT|PATCH|DELETE)$ ) {     return 444;
}
set $origin $http_origin;
' X7 ~. W4 z: ]) t' _/ Fif ($origin !~ '^https?://(subdom1|subdom2)\.yourdom\.zone$') {
* r' {/ r. ]  u2 H# U1 h% a* R2 O     set $origin 'https://default.yourdom.zone';
5 R0 r  T  k! N$ [}
if ($request_method = 'OPTIONS') {
) m" L( i, X7 g/ M, N, S     add_header 'Access-Control-Allow-Origin' "$origin" always;
# U& q! v* P; P' _& M) t     add_header 'Access-Control-Allow-Methods' 'GET, POST, PATCH, PUT, DELETE, OPTIONS' always;
; L  k+ ]! C; b/ h6 b- y) Z     add_header 'Access-Control-Allow-Headers' 'Content-Type, Accept, Authorization' always;
     add_header 'Access-Control-Allow-Credentials' 'true' always;
     add_header Access-Control-Max-Age 1728000;   #20 days   
     add_header Content-Type 'text/plain charset=UTF-8';
. o% x% X. e3 w; m. r1 J$ ~     add_header Content-Length 0;
     return 204;
3 d8 k6 Y) {$ n$ v$ ~( w3 Q4 L1 D9 z}
if ($request_method ~ '(GET|POST|PATCH|PUT|DELETE)') {
4 I* Z# N9 o8 t5 T. s     add_header Access-Control-Allow-Origin "$origin" always;
. j5 R+ X& [& G' y     add_header Access-Control-Allow-Methods 'GET, POST, PATCH, PUT, DELETE, OPTIONS' always;
     add_header Access-Control-Allow-Headers 'Content-Type, Accept, Authorization' always;
+ ?7 {# n! s5 f. k     add_header Access-Control-Allow-Credentials true always;
$ {6 }& Y5 `! a; y2 Z7 o! H- I7 @7 j}

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

# based on https://gist.github.com/4165271/
: j. e0 j# Z( d/ b3 o#
2 q/ ?9 o; m9 S5 P- U' Q$ l# Slightly tighter CORS config for nginx
#
; G, o; l( @/ d5 u; }  S3 I# 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
7 [! S$ q" n% J# a# Access-Control-Allow-Origin headers, several browsers (well, at least Firefox)
' z4 u. c4 x* [& W# don't seem to play nicely with this.
* G2 b; k) F( q/ L% |#
# To avoid the use of 'Access-Control-Allow-Origin: *', use a simple-ish whitelisting
# method to control access instead.
#
% ?# N& b+ x; a& z+ ?# NB: This relies on the use of the 'Origin' HTTP Header.

location / {

* g, ~2 b1 c7 D/ P( p$ x  n' ~    if ($http_origin ~* (^https?://([^/]+\.)*(domainone|domaintwo)\.com$)) {
2 m  {1 B# V1 r& y5 Q7 o        set $cors "true";
5 H; A7 _  t. h" P$ R  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') {
+ E4 U4 e& `0 @2 j1 h6 C, V# h9 q0 D        set $cors "${cors}options";
# \: Q  c1 F7 f! x) k& v: O# Y% w    }
4 C! D& h8 @1 s: ~- [    if ($request_method = 'GET') {
        set $cors "${cors}get";
. W2 c% n, a: r2 S0 d    }
( u, E5 r) o% l* F3 a    if ($request_method = 'POST') {
        set $cors "${cors}post";
6 I' R- W0 P0 K# u' t' B    }
# V+ b( V/ A2 b
5 D0 i6 x% N  R1 W1 B9 y0 ]    if ($cors = "true") {
        # Catch all incase there's a request method we're not dealing with properly
/ @; T! N; M: N( [0 i        add_header 'Access-Control-Allow-Origin' "$http_origin";
    }

    if ($cors = "trueget") {
        add_header 'Access-Control-Allow-Origin' "$http_origin";
        add_header 'Access-Control-Allow-Credentials' 'true';
  X3 d) q! g* ?+ v8 X/ k        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';
0 u; h/ n- L; T) t5 c& O    }
$ z7 D3 ?) {7 c8 d( Q
" N4 v$ k. U& [/ C    if ($cors = "trueoptions") {
        add_header 'Access-Control-Allow-Origin' "$http_origin";
- S' g( t5 ?' y. }. X4 F6 K
/ L9 u) c9 t, ]: t( c* |        #
$ x# m& g, Y. m) |; d& q        # Om nom nom cookies
        #
        add_header 'Access-Control-Allow-Credentials' 'true';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
: r/ r  X" ~' S& ]- Y) n
        #
        # 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';
$ h9 `) r5 r8 I, M
# o8 I+ b9 g, u        #
        # Tell client that this pre-flight info is valid for 20 days
        #
+ y" B8 U' W: S$ U3 P        add_header 'Access-Control-Max-Age' 1728000;
- L( A  m* u4 z  I! j0 y3 X6 t        add_header 'Content-Type' 'text/plain charset=UTF-8';
        add_header 'Content-Length' 0;
        return 204;
' E' c5 w( G9 X9 [7 U: a5 Z    }
' ^, ?! ~+ ?7 R/ l4 z5 H
    if ($cors = "truepost") {
        add_header 'Access-Control-Allow-Origin' "$http_origin";
        add_header 'Access-Control-Allow-Credentials' 'true';
( l* Y/ k9 `( K- l) G% o        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';
& g5 d( o1 C# ]& I1 J    }

}

( h% x( P6 \$ n% k