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

IT_man

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

# CORS header support
; _2 U$ A9 V- @( A0 M4 J6 `#
( u( X  N" s5 Z& p3 a! I9 T# One way to use this is by placing it into a file called "cors_support"
. d% L/ f7 s/ [1 D; a2 P# under your Nginx configuration directory and placing the following
# statement inside your **location** block(s):
#
+ ]6 f4 A+ R9 u4 l! d# @#   include cors_support;
8 z. f" X, l& {: U- u#
# 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.
#
$ e8 O) g$ j2 @# For more information on CORS, please see: http://enable-cors.org/
# Forked from this Gist: https://gist.github.com/michiel/1064640
) j6 t" F3 n7 F8 m: M- M#

set $cors '';
if ($http_origin ~ '^https?://(localhost|www\.yourdomain\.com|www\.yourotherdomain\.com)$') {
; O% v: P2 U  M- t        set $cors 'true';
7 }0 v- r) p* a# X}

if ($cors = 'true') {
2 i; l8 V& o- y$ G. d9 V# e; K        add_header 'Access-Control-Allow-Origin' "$http_origin" always;
        add_header 'Access-Control-Allow-Credentials' 'true' always;
. X# }5 e+ V' v+ H        add_header 'Access-Control-Allow-Methods' 'GET, POST, PUT, DELETE, OPTIONS' always;
6 }0 p. Q* L7 k$ \3 s0 h        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;
+ @* G" t5 v) Q& |' r1 g        # required to be able to read Authorization header in frontend
# x: Z* j" t- d! ?  H" B0 j, E! t        #add_header 'Access-Control-Expose-Headers' 'Authorization' always;
}
$ m8 W; C4 `. l" b5 ?8 H
# c  V' `7 c9 x8 U" zif ($request_method = 'OPTIONS') {
2 l1 a3 r1 d# ~. b& ?        # Tell client that this pre-flight info is valid for 20 days
+ e( N# _9 L6 Q+ L6 P        add_header 'Access-Control-Max-Age' 1728000;
9 I! i2 z% O5 A4 ^2 J: u) Z* ^        add_header 'Content-Type' 'text/plain charset=UTF-8';
        add_header 'Content-Length' 0;
3 y" T4 e  G; \6 G! D* P) h* a4 n5 c, U        return 204;
6 d" K6 k$ ]8 S' x7 |8 x" T}

https://gist.github.com/Stanback/7145487#file-nginx-conf 的討論範例:
/ p  k9 I& N. O; l6 y5 N

if ( $request_method !~ ^(GET|POST|HEAD|OPTIONS|PUT|PATCH|DELETE)$ ) {     return 444;
}
& P; N3 i& J7 v6 S" Sset $origin $http_origin;
if ($origin !~ '^https?://(subdom1|subdom2)\.yourdom\.zone$') {
1 e* c* K9 P  _7 G     set $origin 'https://default.yourdom.zone';
}
if ($request_method = 'OPTIONS') {
     add_header 'Access-Control-Allow-Origin' "$origin" always;
8 |+ ]0 T& Q& r8 @0 f     add_header 'Access-Control-Allow-Methods' 'GET, POST, PATCH, PUT, DELETE, OPTIONS' always;
     add_header 'Access-Control-Allow-Headers' 'Content-Type, Accept, Authorization' always;
! S8 F6 o3 G( o# \2 @' m     add_header 'Access-Control-Allow-Credentials' 'true' always;
     add_header Access-Control-Max-Age 1728000;   #20 days   
0 l' d8 O6 d% P! H: s     add_header Content-Type 'text/plain charset=UTF-8';
     add_header Content-Length 0;
3 i" V& b; P0 K8 E9 S5 N& C+ f     return 204;
}
3 q0 P; L% j6 B( l6 d, uif ($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;
     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
  H6 a0 k! j# Y# H: ~; g#
# 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
2 ]6 W( m' S  S# 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
# method to control access instead.
#
# NB: This relies on the use of the 'Origin' HTTP Header.

location / {

. O2 E: l0 q; b( q    if ($http_origin ~* (^https?://([^/]+\.)*(domainone|domaintwo)\.com$)) {
9 D$ n- D% h8 K: t( c6 p( j- A        set $cors "true";
; p$ n8 z  p  s% ^    }
6 i- c, u' }# B4 d
    # Nginx doesn't support nested If statements. This is where things get slightly nasty.
; C+ B" |# }8 h; |* }+ K/ g    # Determine the HTTP request method used
4 {6 C; E  G. e1 p- _    if ($request_method = 'OPTIONS') {
7 S3 m- F$ w6 _3 E. R) P        set $cors "${cors}options";
    }
    if ($request_method = 'GET') {
        set $cors "${cors}get";
: k( z/ _# _6 q8 P    }
8 }1 I7 u  ]0 h    if ($request_method = 'POST') {
        set $cors "${cors}post";
    }
4 J! s7 t0 o9 |  L
1 U' E' h4 I2 M" r* C    if ($cors = "true") {
& X; R% Z: e/ I3 v. f5 j        # Catch all incase there's a request method we're not dealing with properly
  v0 a; `1 e. c0 M' d! S1 ^5 b- o        add_header 'Access-Control-Allow-Origin' "$http_origin";
- Y2 v2 F; ?5 b7 c( s/ A: e& ]    }

- M& P+ R) L% v9 m  O    if ($cors = "trueget") {
  A0 }  P; \2 l+ H, t0 l        add_header 'Access-Control-Allow-Origin' "$http_origin";
        add_header 'Access-Control-Allow-Credentials' 'true';
        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';
/ [" L  M5 ?2 V$ ~, w    }
6 k* D* Y- Y3 E
& U9 M/ P$ f. m+ U* N    if ($cors = "trueoptions") {
7 c& V" [. k+ D2 e2 _; c% h: o+ ^        add_header 'Access-Control-Allow-Origin' "$http_origin";
3 B+ g6 _% }/ o5 _2 |4 e% [$ B9 V
  H- o9 Q3 |' m5 b1 @        #
        # Om nom nom cookies
, y2 E* I8 m9 X5 G- E" c        #
        add_header 'Access-Control-Allow-Credentials' 'true';
- x0 o, o- ~7 ]7 ]5 p        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';

        #
& g/ g; h; G; ~8 ~# H        # Custom headers and headers various browsers *should* be OK with but aren't
        #
, G* n% m! @" C        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';

8 P3 W- i* U; O  g        #
        # 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;
' o% D% C3 n8 d( D    }
+ |& D# W! @  y
    if ($cors = "truepost") {
) o2 a# m$ t' a        add_header 'Access-Control-Allow-Origin' "$http_origin";
5 M+ g3 `! V; O8 ^0 V. b        add_header 'Access-Control-Allow-Credentials' 'true';
        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';
- A1 x: E- L6 H    }
2 t' P. H$ Y( W8 W. Y
}

7 l$ J8 O' l; R% a8 T) p' l' T
  X  e" A- y2 _