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

IT_man

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

# CORS header support
1 {" l8 J( u5 t/ B" o+ T#
( ], ^0 Q9 I/ U: R3 e2 F2 `3 `# One way to use this is by placing it into a file called "cors_support"
4 w  G5 G0 x' {9 l# R1 x) E* Z# under your Nginx configuration directory and placing the following
3 o6 R# \9 M' S0 K$ y9 M3 M4 m# statement inside your **location** block(s):
/ b. b, Y$ ^8 O$ c#
#   include cors_support;
#
: u- ?9 O6 `" [3 k4 b% v- Z* |# _# 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.
#
' S. L! R  B  E$ z! e# For more information on CORS, please see: http://enable-cors.org/
/ \% J" O, ?- }( B# Forked from this Gist: https://gist.github.com/michiel/1064640
#

set $cors '';
# o$ B  g. ]1 [: X" `if ($http_origin ~ '^https?://(localhost|www\.yourdomain\.com|www\.yourotherdomain\.com)$') {
% `& d/ C/ }0 H' Y7 i( |! v0 @' n        set $cors 'true';
) O" E, ]8 u: Q8 n}

if ($cors = 'true') {
1 v* g5 i1 V1 \. N- H% v+ J9 H        add_header 'Access-Control-Allow-Origin' "$http_origin" always;
. A2 N# v( u' W# o        add_header 'Access-Control-Allow-Credentials' 'true' always;
9 V0 a1 k! x3 ?- O0 V' ]) X" p. 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
- w% n* m5 v2 f        #add_header 'Access-Control-Expose-Headers' 'Authorization' always;
}
) {( H' `% N- P$ W. c" N- Q
2 z6 j8 e6 z5 u# u% w9 bif ($request_method = 'OPTIONS') {
4 F: `1 N. `) X7 p  p1 ^' ]        # 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';
5 A- `; e  W  Z9 N        add_header 'Content-Length' 0;
        return 204;
6 {" v  o, O6 ?. \4 R}

https://gist.github.com/Stanback/7145487#file-nginx-conf 的討論範例:

if ( $request_method !~ ^(GET|POST|HEAD|OPTIONS|PUT|PATCH|DELETE)$ ) {     return 444;
}
8 Z  v- o' u% f- n8 j* O3 _set $origin $http_origin;
if ($origin !~ '^https?://(subdom1|subdom2)\.yourdom\.zone$') {
     set $origin 'https://default.yourdom.zone';
}
if ($request_method = 'OPTIONS') {
; N7 R) A' o9 v5 J" k     add_header 'Access-Control-Allow-Origin' "$origin" always;
$ s0 _3 r, u& \8 h; c     add_header 'Access-Control-Allow-Methods' 'GET, POST, PATCH, PUT, DELETE, OPTIONS' always;
4 E2 P: r0 X; N$ h     add_header 'Access-Control-Allow-Headers' 'Content-Type, Accept, Authorization' always;
- l8 t: X3 l7 N2 _6 P8 v" b8 S  Q     add_header 'Access-Control-Allow-Credentials' 'true' always;
     add_header Access-Control-Max-Age 1728000;   #20 days   
( @" G! X* f% n0 f7 q; i$ t     add_header Content-Type 'text/plain charset=UTF-8';
3 R" a* N7 U- y- B" ]. c' ?     add_header Content-Length 0;
, r( q0 L4 e% w2 o     return 204;
) \$ z$ g2 L) G}
if ($request_method ~ '(GET|POST|PATCH|PUT|DELETE)') {
. L4 m2 l! Z7 n& A% y     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;
* ]) `, I1 z& y- r6 e. s, V     add_header Access-Control-Allow-Credentials true always;
}

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

# based on https://gist.github.com/4165271/
7 d. V, \1 x. f* k  X3 o. S  G0 Y#
# Slightly tighter CORS config for nginx
#
/ C" _' {" L8 Y4 m! Z) Q+ A0 i# A modification of https://gist.github.com/1064640/ to include a white-list of URLs
#
1 o6 k2 I8 ]9 k# 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)
4 G% r, ~# U2 `( k) ~5 L# 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.
; g) e& y; ~; ?& ~9 \#
# NB: This relies on the use of the 'Origin' HTTP Header.

8 R/ K' o; E) G: m# mlocation / {

9 e1 X- u3 D/ L. B6 Q& m3 t& [% R    if ($http_origin ~* (^https?://([^/]+\.)*(domainone|domaintwo)\.com$)) {
        set $cors "true";
/ t8 j. W% D$ {& I/ E. [# B    }

. D; N9 n; G, N' d% k- \( \    # Nginx doesn't support nested If statements. This is where things get slightly nasty.
+ l  G+ Y' U6 f2 S& }  L/ m    # Determine the HTTP request method used
    if ($request_method = 'OPTIONS') {
        set $cors "${cors}options";
    }
& u( {6 \! d. n2 w3 ^% X6 U    if ($request_method = 'GET') {
+ c+ e" u; }! P        set $cors "${cors}get";
    }
1 [' l' r) z3 \$ g$ a, ]# U    if ($request_method = 'POST') {
        set $cors "${cors}post";
    }

    if ($cors = "true") {
. H5 Z9 e) d) B; p& Y  E        # Catch all incase there's a request method we're not dealing with properly
        add_header 'Access-Control-Allow-Origin' "$http_origin";
3 s/ Z. X% s$ U: k0 n/ x    }

    if ($cors = "trueget") {
        add_header 'Access-Control-Allow-Origin' "$http_origin";
9 C2 ]% W( a7 X9 u        add_header 'Access-Control-Allow-Credentials' 'true';
$ z0 X& e/ v$ }/ R        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
, ^% M. x/ `7 I1 S4 L" d        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
    }

0 f0 {3 C8 m6 S% b, T6 H' a8 B6 C    if ($cors = "trueoptions") {
5 R: s6 T6 x8 D& {. E, K% `, ^2 U        add_header 'Access-Control-Allow-Origin' "$http_origin";
" j0 X- L( l, A1 a7 a
. h8 k$ Y4 M) d2 d! s4 o2 R        #
        # Om nom nom cookies
3 ^0 G% q0 k* j- z( N% o, ]        #
        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';
" p: y1 Y0 }: J' ~
        #
        # Tell client that this pre-flight info is valid for 20 days
* W# A2 G* P8 V2 _% p, C$ p        #
        add_header 'Access-Control-Max-Age' 1728000;
2 F2 p( J1 E- K& ~5 O7 t        add_header 'Content-Type' 'text/plain charset=UTF-8';
        add_header 'Content-Length' 0;
        return 204;
+ N$ M4 ?; |% q4 f    }
9 X+ Y, w0 c7 D9 ^
    if ($cors = "truepost") {
4 T8 I" r1 D# Q- ^        add_header 'Access-Control-Allow-Origin' "$http_origin";
        add_header 'Access-Control-Allow-Credentials' 'true';
  c* U; G6 U% K, _) l. R/ a# {% w6 e3 x        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 N+ C& a" a$ F2 {3 x    }
) ~& S* w8 T' Y5 U' J
}

1 J: X1 Z7 J8 [0 W& S2 }+ v