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

IT_man

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


( d$ f4 H+ P: @

# CORS header support
; f7 S! G1 _5 w/ m' R4 U#
# One way to use this is by placing it into a file called "cors_support"
3 E9 H2 J0 @0 w# }+ a' q* v5 h" B# under your Nginx configuration directory and placing the following
9 Z6 ~5 v+ P" \7 |5 [; e9 s* f# statement inside your **location** block(s):
#
, z  |: A6 D) w" S' [#   include cors_support;
: h. w% D( H; Z9 E  H#
# As of Nginx 1.7.5, add_header supports an "always" parameter which
9 ?- w! z, O2 I8 i$ _# 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
$ ^; }5 N2 M% y/ `9 a#
5 L" P; K" K, a4 f
/ I! D1 @9 _; u; x* Z% j% qset $cors '';
if ($http_origin ~ '^https?://(localhost|www\.yourdomain\.com|www\.yourotherdomain\.com)$') {
: J" E! Q) D4 O  X4 Z; E* _        set $cors 'true';
}
! c8 ^$ N& H# f" R% h3 z# K' c6 \
if ($cors = 'true') {
        add_header 'Access-Control-Allow-Origin' "$http_origin" always;
* |( |' B$ w' J2 v& S0 p        add_header 'Access-Control-Allow-Credentials' 'true' always;
2 T3 d  Z6 s) }, O, F# ~        add_header 'Access-Control-Allow-Methods' 'GET, POST, PUT, DELETE, OPTIONS' always;
( e" q- _+ V% G7 C5 Q% b/ v' V        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;
+ v0 [4 d4 V; f/ R$ H        # required to be able to read Authorization header in frontend
        #add_header 'Access-Control-Expose-Headers' 'Authorization' always;
}

if ($request_method = 'OPTIONS') {
$ S2 T* e' W/ Z5 c* `        # Tell client that this pre-flight info is valid for 20 days
        add_header 'Access-Control-Max-Age' 1728000;
) v! E* I9 p+ m        add_header 'Content-Type' 'text/plain charset=UTF-8';
3 o' L% a9 y2 c4 A/ R5 \: X        add_header 'Content-Length' 0;
; N# Z; X' d; i! d& ^        return 204;
: Y. ]% n3 k" i3 q  v9 t3 f5 A& ?9 f3 c! x}

https://gist.github.com/Stanback/7145487#file-nginx-conf 的討論範例:
, ^- v4 d  z3 C, O& J

if ( $request_method !~ ^(GET|POST|HEAD|OPTIONS|PUT|PATCH|DELETE)$ ) {     return 444;
# C! l" Z% d, X, G) O: k}
set $origin $http_origin;
if ($origin !~ '^https?://(subdom1|subdom2)\.yourdom\.zone$') {
     set $origin 'https://default.yourdom.zone';
}
if ($request_method = 'OPTIONS') {
, ?! j. j  F7 l) i$ A3 y2 c) ~' k     add_header 'Access-Control-Allow-Origin' "$origin" always;
! Q# Y' C& X3 ?! x4 [8 T$ M     add_header 'Access-Control-Allow-Methods' 'GET, POST, PATCH, PUT, DELETE, OPTIONS' always;
     add_header 'Access-Control-Allow-Headers' 'Content-Type, Accept, Authorization' always;
$ Q% p% |# e7 ], h     add_header 'Access-Control-Allow-Credentials' 'true' always;
: `  [. m/ s  c1 K' I3 i     add_header Access-Control-Max-Age 1728000;   #20 days   
5 ~1 C4 f% }  @- B- ]& U* ^     add_header Content-Type 'text/plain charset=UTF-8';
     add_header Content-Length 0;
     return 204;
}
if ($request_method ~ '(GET|POST|PATCH|PUT|DELETE)') {
, X# S# a7 B/ q3 Y$ m  e     add_header Access-Control-Allow-Origin "$origin" always;
5 ~9 |5 n" `1 A1 ~/ I+ q# c     add_header Access-Control-Allow-Methods 'GET, POST, PATCH, PUT, DELETE, OPTIONS' always;
     add_header Access-Control-Allow-Headers 'Content-Type, Accept, Authorization' always;
# x6 y, p* H9 E0 Q9 C8 w+ ?     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
" }9 R& |' A- j4 r! V) n- j#
# A modification of https://gist.github.com/1064640/ to include a white-list of URLs
#
$ o/ w, I: C- E4 M) x# 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)
, A7 T; B2 n. r# don't seem to play nicely with this.
#
1 Z' h7 }6 V6 n) M: i6 E2 s; Q# 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.
" ~+ i- n! e9 J: A/ @  ~  `$ `  @% `
) e- F% S+ Q2 s% W9 O2 v' alocation / {

8 w: |7 t) l; B# e0 O+ u0 S' I% M    if ($http_origin ~* (^https?://([^/]+\.)*(domainone|domaintwo)\.com$)) {
        set $cors "true";
    }
* ^5 S' E' e0 g( f+ X7 u
( w2 L( m! L4 N5 o    # Nginx doesn't support nested If statements. This is where things get slightly nasty.
    # Determine the HTTP request method used
$ k8 r6 E3 y, r3 {2 Q; }    if ($request_method = 'OPTIONS') {
        set $cors "${cors}options";
5 E0 G9 K& F& m. {    }
    if ($request_method = 'GET') {
* J7 r+ y5 ^9 t8 U        set $cors "${cors}get";
    }
    if ($request_method = 'POST') {
        set $cors "${cors}post";
    }

' Z( f; F' V2 g; Y    if ($cors = "true") {
2 Q9 C1 g4 X. u( ]6 @        # Catch all incase there's a request method we're not dealing with properly
1 {& Y4 f- i3 b8 O3 e: N        add_header 'Access-Control-Allow-Origin' "$http_origin";
+ `$ v& X) ]8 @) ^    }
$ ?. v* T0 r! y
% |! F  D4 p. A4 u! M: h) y2 p/ g    if ($cors = "trueget") {
9 o) i; D" v$ c( Q        add_header 'Access-Control-Allow-Origin' "$http_origin";
        add_header 'Access-Control-Allow-Credentials' 'true';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
8 y- @( s9 f$ R, p1 g        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
4 q. l5 a% `% @' L$ {- P+ C    }

' J4 i! e9 E8 I0 h4 D0 S" b' C    if ($cors = "trueoptions") {
# P/ x5 q- `7 d6 U) n        add_header 'Access-Control-Allow-Origin' "$http_origin";

; A& M' v" j& i        #
        # Om nom nom cookies
        #
0 t9 r# X- @4 q1 ^        add_header 'Access-Control-Allow-Credentials' 'true';
        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';

' d& ]- O4 J4 L# J; d( m        #
5 b3 d& {* i" ~4 p5 p0 r7 c/ T        # Custom headers and headers various browsers *should* be OK with but aren't
        #
) R6 W: `8 ^2 R# h/ R3 m$ e6 w) T        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';

        #
3 d% E- p( s5 w4 e: ~5 i        # Tell client that this pre-flight info is valid for 20 days
        #
9 J/ M( Z; e  ]2 ~% B7 H! _        add_header 'Access-Control-Max-Age' 1728000;
5 H) @8 J6 X% P        add_header 'Content-Type' 'text/plain charset=UTF-8';
6 G, q. b+ I0 z# e' H        add_header 'Content-Length' 0;
/ z) ?0 L" L. l2 u' [3 U7 b: b        return 204;
5 R, T2 b9 P% V8 v) g/ N0 Q1 @    }

    if ($cors = "truepost") {
+ s4 r8 J' B' D        add_header 'Access-Control-Allow-Origin' "$http_origin";
        add_header 'Access-Control-Allow-Credentials' 'true';
" }; O5 d$ M: l: C: u3 X4 l        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
+ \0 E9 P! L* i0 h: Q. I        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
    }
0 t+ {/ g! N7 O& f" m
}

! w3 X) u, U1 s& M/ f; C2 `