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

IT_man

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

/ r* v' a5 r# B8 \7 ^! c
9 S) n; P/ I4 ]/ w

# CORS header support
1 b& {/ w2 C$ I" H8 ^2 v#
# One way to use this is by placing it into a file called "cors_support"
/ V: c7 |7 a" W$ {9 p* D# under your Nginx configuration directory and placing the following
# statement inside your **location** block(s):
#
1 D: l5 r: O; W- Q#   include cors_support;
#
# As of Nginx 1.7.5, add_header supports an "always" parameter which
, Q- h6 X( E; p6 W. Y$ [& o# allows CORS to work if the backend returns 4xx or 5xx status code.
! R1 k/ v7 p3 c( H#
- X) K8 `  G$ z( r$ u# l- \( L# For more information on CORS, please see: http://enable-cors.org/
# Forked from this Gist: https://gist.github.com/michiel/1064640
#

# S' c/ e, B, h9 w/ M) K, Nset $cors '';
! ~4 ~: S& _- c/ Eif ($http_origin ~ '^https?://(localhost|www\.yourdomain\.com|www\.yourotherdomain\.com)$') {
        set $cors 'true';
}

& V2 F4 O& h& @* E& ~if ($cors = 'true') {
        add_header 'Access-Control-Allow-Origin' "$http_origin" always;
0 C/ ^6 B# S5 s5 {+ c  S5 t0 R& b% `6 L        add_header 'Access-Control-Allow-Credentials' 'true' always;
5 B2 A/ ?' P6 ?$ y) O7 t        add_header 'Access-Control-Allow-Methods' 'GET, POST, PUT, DELETE, OPTIONS' always;
; I8 A, V; v: _- ?) F% D7 t9 ]        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
        #add_header 'Access-Control-Expose-Headers' 'Authorization' always;
3 H7 }9 s4 U3 i% `}
: ~1 ]  c0 h$ A$ |- d
if ($request_method = 'OPTIONS') {
  J* w& h- d& }' [- O- c        # Tell client that this pre-flight info is valid for 20 days
0 w, M7 H. g0 M6 h  ~5 r7 n0 O        add_header 'Access-Control-Max-Age' 1728000;
        add_header 'Content-Type' 'text/plain charset=UTF-8';
        add_header 'Content-Length' 0;
        return 204;
! |. b( r  D2 V2 S) H' B3 e}

https://gist.github.com/Stanback/7145487#file-nginx-conf 的討論範例:
7 r; F) ~# I, o! C' p9 \3 i

if ( $request_method !~ ^(GET|POST|HEAD|OPTIONS|PUT|PATCH|DELETE)$ ) {     return 444;
4 C8 b1 _+ I9 @}
set $origin $http_origin;
if ($origin !~ '^https?://(subdom1|subdom2)\.yourdom\.zone$') {
- b: a, F+ n$ L+ o3 q     set $origin 'https://default.yourdom.zone';
. u6 `+ ?% `! N: p}
if ($request_method = 'OPTIONS') {
( |. R9 o. f( I' W3 T; M     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;
& ~5 p0 L9 Y3 `. @+ D1 j" m     add_header 'Access-Control-Allow-Credentials' 'true' always;
" G8 l6 ~$ e6 B; u) j; ~4 ^- i     add_header Access-Control-Max-Age 1728000;   #20 days   
     add_header Content-Type 'text/plain charset=UTF-8';
1 D% u7 S5 k$ v8 s1 ~( G     add_header Content-Length 0;
     return 204;
}
if ($request_method ~ '(GET|POST|PATCH|PUT|DELETE)') {
4 }. y: O& _8 T( C. z- ]     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;
) x- G  b  x# R2 i# B7 m     add_header Access-Control-Allow-Credentials true always;
}

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

# based on https://gist.github.com/4165271/
#
; S' P8 x+ W4 H% R; H# B& H# Slightly tighter CORS config for nginx
+ x: _; Y& O! G7 x1 g6 j! j#
2 C9 @3 y( q3 Y7 H4 F# A modification of https://gist.github.com/1064640/ to include a white-list of URLs
#
. E: ]  V4 Y: L; o- V6 i  v# Despite the W3C guidance suggesting that a list of origins can be passed as part of
, D4 l, X0 F2 _: U# 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
9 P( K  [6 l; Z4 ]3 j: P1 h2 t6 F+ Q# method to control access instead.
0 k* w& L; \/ u1 q$ m" S#
! y5 K4 s) h2 ~+ k* q7 M, u, i# NB: This relies on the use of the 'Origin' HTTP Header.
& _: u( u  L% {2 `
6 S4 d9 x- W# tlocation / {
6 v" n+ W5 l, z' @
, |4 O+ R) r3 j: M5 Y; ?    if ($http_origin ~* (^https?://([^/]+\.)*(domainone|domaintwo)\.com$)) {
* v# u9 u5 i! m8 D        set $cors "true";
    }

/ G6 s) h" Q- p9 c& P/ w- \5 W    # Nginx doesn't support nested If statements. This is where things get slightly nasty.
: J. s4 f  Q: I# I+ ]3 E6 L5 T    # Determine the HTTP request method used
: N* s. G6 {9 W8 w4 \: n* L    if ($request_method = 'OPTIONS') {
) E7 ~  j1 t" g        set $cors "${cors}options";
    }
    if ($request_method = 'GET') {
& m2 W( d- G5 m6 o2 M5 @        set $cors "${cors}get";
  I- J& g; ~/ x8 {6 c    }
    if ($request_method = 'POST') {
1 Y' R- z. q6 h3 P$ w5 h% T7 \        set $cors "${cors}post";
, f: G9 U. g. G4 A: r* O+ j/ r    }

    if ($cors = "true") {
        # Catch all incase there's a request method we're not dealing with properly
& Y4 Y# E6 V9 Y$ A0 U) g' _- n        add_header 'Access-Control-Allow-Origin' "$http_origin";
2 Y& J5 _9 K  y% j# }; P( Z7 |8 C! |) n: }    }
; h, p1 _9 L$ |: C8 V
+ \- o6 i. o& R1 @1 ^4 @    if ($cors = "trueget") {
        add_header 'Access-Control-Allow-Origin' "$http_origin";
        add_header 'Access-Control-Allow-Credentials' 'true';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
& [$ A. P7 w* s# W* c, P        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
' \5 B' K8 p' B7 i# j8 F, _    }

    if ($cors = "trueoptions") {
        add_header 'Access-Control-Allow-Origin' "$http_origin";
, ]" J6 S, [+ `* {# d8 F
$ Z4 `* X  j: |# n" W5 r        #
        # Om nom nom cookies
% I8 {' f; @- M4 C9 ?9 c        #
. m3 Q5 ~/ U% {  K8 @/ w  g8 u        add_header 'Access-Control-Allow-Credentials' 'true';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';

        #
, V: O; B; e' U        # Custom headers and headers various browsers *should* be OK with but aren't
        #
' f5 A, d8 o: ~- P+ g        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';

0 y( [  }% F1 ~* A        #
( U3 q/ e. P) l8 t+ X/ m        # Tell client that this pre-flight info is valid for 20 days
, ^7 `: D1 i3 Z. y5 v) {" [* A, J        #
; }# {" v& Y% j% P* N# K' X: r        add_header 'Access-Control-Max-Age' 1728000;
5 n: Q/ V; d" L& E8 t        add_header 'Content-Type' 'text/plain charset=UTF-8';
        add_header 'Content-Length' 0;
$ I& t4 G0 \) [( {' z7 V9 w* T6 I        return 204;
    }

    if ($cors = "truepost") {
        add_header 'Access-Control-Allow-Origin' "$http_origin";
* Q0 {2 y% C9 {# w6 }* p        add_header 'Access-Control-Allow-Credentials' 'true';
: [# a/ w- X; ?: i  z) R6 H        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';
4 J  U7 Q  f0 k/ N8 _    }

}

/ v9 ~5 R& k) S; r2 J$ r