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

IT_man

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

) H/ ]: W: o- f  X5 q
' ]2 q' m# l9 r  c

# CORS header support
* Y( p, }2 Z9 |. W#
/ q$ ?2 u' Y* w3 J# One way to use this is by placing it into a file called "cors_support"
  ~- x; l7 G3 s7 X- F, O8 S# under your Nginx configuration directory and placing the following
# statement inside your **location** block(s):
" p6 h  V; ^: p" X#
#   include cors_support;
# [& h7 Z; N+ A8 M#
. O: Q$ T+ o' N8 \$ Y# 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.
#
2 ?/ j( g7 f. l8 `5 c# For more information on CORS, please see: http://enable-cors.org/
9 l2 N7 g4 f& j& S# Forked from this Gist: https://gist.github.com/michiel/1064640
#

set $cors '';
if ($http_origin ~ '^https?://(localhost|www\.yourdomain\.com|www\.yourotherdomain\.com)$') {
        set $cors 'true';
}
) h! @$ @: P7 T9 t3 p8 p; [. Q
if ($cors = 'true') {
3 e; Q4 P9 J" l* k6 j' M        add_header 'Access-Control-Allow-Origin' "$http_origin" always;
; w3 t( t2 m: t$ g1 u        add_header 'Access-Control-Allow-Credentials' 'true' always;
        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
# S, |! G- ~9 U7 Z) n2 \/ d; a        #add_header 'Access-Control-Expose-Headers' 'Authorization' always;
7 T8 I6 X" i5 U/ P& h}
5 e8 k8 Z7 ~- |; t! J( a
if ($request_method = 'OPTIONS') {
        # Tell client that this pre-flight info is valid for 20 days
, n" a- v6 U$ H/ S        add_header 'Access-Control-Max-Age' 1728000;
# U* K0 a  F& A        add_header 'Content-Type' 'text/plain charset=UTF-8';
        add_header 'Content-Length' 0;
        return 204;
* I  E$ o4 _. d. y* d" c: x}

https://gist.github.com/Stanback/7145487#file-nginx-conf 的討論範例:
1 V2 o" i9 d2 P  J4 o. P

if ( $request_method !~ ^(GET|POST|HEAD|OPTIONS|PUT|PATCH|DELETE)$ ) {     return 444;
7 k0 \. o/ d- W5 F. Q' B) ^}
set $origin $http_origin;
9 T3 M& v+ p& i# |if ($origin !~ '^https?://(subdom1|subdom2)\.yourdom\.zone$') {
% P1 u  n) `3 p1 W& ^/ i) {3 }     set $origin 'https://default.yourdom.zone';
}
, i0 |6 C! V+ D: I- x1 E( nif ($request_method = 'OPTIONS') {
& e  g& I. \6 U( o0 z     add_header 'Access-Control-Allow-Origin' "$origin" always;
' c3 d6 i7 T/ N     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;
; s# M# L! g- d: a8 K4 I" H- n+ l     add_header Access-Control-Max-Age 1728000;   #20 days   
     add_header Content-Type 'text/plain charset=UTF-8';
  K" _5 R2 r+ ^! C/ ^7 {; @     add_header Content-Length 0;
     return 204;
}
* U5 v% _: R0 Z4 t2 C! Gif ($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;
/ @9 |+ {4 t& Y' U; P     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/
#
% s8 M9 m  V+ J( ?" n# Slightly tighter CORS config for nginx
#
  r5 a* @2 L) A/ C# A modification of https://gist.github.com/1064640/ to include a white-list of URLs
; {! H/ n8 r2 l5 u! g/ w, b#
# 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)
# don't seem to play nicely with this.
! ^$ I" W$ k2 P: C& @" A#
. g+ I" L! `4 s+ C5 W: ?4 E# 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.
: J- S, T8 e- ~3 B2 j- A7 i1 n
4 e9 _' }/ ?; Tlocation / {

3 c7 M' P" H, e% [    if ($http_origin ~* (^https?://([^/]+\.)*(domainone|domaintwo)\.com$)) {
        set $cors "true";
    }
! c0 r0 c, c  m. o1 ^
* @. F1 F! n6 R5 t3 X    # Nginx doesn't support nested If statements. This is where things get slightly nasty.
* c0 D% l+ s9 e0 ]2 E% A    # Determine the HTTP request method used
% F6 d3 W( P! i2 Q, M  r    if ($request_method = 'OPTIONS') {
        set $cors "${cors}options";
3 j6 f9 g7 I+ r/ A$ U    }
  O' V7 T* m7 V" e4 a6 p    if ($request_method = 'GET') {
        set $cors "${cors}get";
    }
  o4 C! [) T+ A; Z9 ]2 i    if ($request_method = 'POST') {
$ e5 F, q+ y1 c        set $cors "${cors}post";
    }

    if ($cors = "true") {
        # Catch all incase there's a request method we're not dealing with properly
8 L0 Y2 |$ @8 j+ R7 l# x        add_header 'Access-Control-Allow-Origin' "$http_origin";
    }

3 c. k+ A0 {# [9 u    if ($cors = "trueget") {
        add_header 'Access-Control-Allow-Origin' "$http_origin";
        add_header 'Access-Control-Allow-Credentials' 'true';
8 c2 c* |% {0 N7 [( t/ p        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
2 R9 y2 _) B6 S; p# p( l        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';
    }
, y$ [. L* w& R- [
    if ($cors = "trueoptions") {
0 J0 @  `$ n# M5 r9 O7 i        add_header 'Access-Control-Allow-Origin' "$http_origin";
+ b. u% k% B/ R* H9 Z" j. ^! x
& c( v# J' C; @6 t; ~2 C        #
        # Om nom nom cookies
        #
        add_header 'Access-Control-Allow-Credentials' 'true';
3 U, [6 l: v( p3 y( G( o3 `2 L        add_header 'Access-Control-Allow-Methods' 'GET, POST, OPTIONS';
$ `& W" g# H% T7 Q" x
        #
        # Custom headers and headers various browsers *should* be OK with but aren't
2 H( ^' d+ V! Q8 R        #
1 d% J7 {+ c" I4 {: {        add_header 'Access-Control-Allow-Headers' 'DNT,X-CustomHeader,Keep-Alive,User-Agent,X-Requested-With,If-Modified-Since,Cache-Control,Content-Type';

        #
        # 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;
9 ?* D( w$ Y$ \0 S0 P        return 204;
# Q; r6 U3 h; u* o$ g    }

8 h" X0 B3 X9 e( T# W% @    if ($cors = "truepost") {
        add_header 'Access-Control-Allow-Origin' "$http_origin";
$ E! l  h  K& w! t" s9 _& s        add_header 'Access-Control-Allow-Credentials' 'true';
: M% L. q, d# X2 l        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';
" N0 {2 s6 y! {, _    }

; o& |' H/ i+ [/ U, {4 U9 d8 y}