-
Notifications
You must be signed in to change notification settings - Fork 102
/
README
1080 lines (728 loc) · 30 KB
/
README
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
768
769
770
771
772
773
774
775
776
777
778
779
780
781
782
783
784
785
786
787
788
789
790
791
792
793
794
795
796
797
798
799
800
801
802
803
804
805
806
807
808
809
810
811
812
813
814
815
816
817
818
819
820
821
822
823
824
825
826
827
828
829
830
831
832
833
834
835
836
837
838
839
840
841
842
843
844
845
846
847
848
849
850
851
852
853
854
855
856
857
858
859
860
861
862
863
864
865
866
867
868
869
870
871
872
873
874
875
876
877
878
879
880
881
882
883
884
885
886
887
888
889
890
891
892
893
894
895
896
897
898
899
900
901
902
903
904
905
906
907
908
909
910
911
912
913
914
915
916
917
918
919
920
921
922
923
924
925
926
927
928
929
930
931
932
933
934
935
936
937
938
939
940
941
942
943
944
945
946
947
948
949
950
951
952
953
954
955
956
957
958
959
960
961
962
963
964
965
966
967
968
969
970
971
972
973
974
975
976
977
978
979
980
981
982
983
984
985
986
987
988
989
990
991
992
993
994
995
996
997
998
999
1000
Name
ngx_set_misc - Various set_xxx directives added to nginx's rewrite
module (md5/sha1, sql/json quoting, and many more)
*This module is not distributed with the Nginx source.* See the
installation instructions.
Version
This document describes set-misc-nginx-module v0.22rc8
(<https://github.com/agentzh/set-misc-nginx-module/tags>) released on 10
May 2012.
Synopsis
location /foo {
set $a $arg_a;
set_if_empty $a 56;
# GET /foo?a=32 will yield $a == 32
# while GET /foo and GET /foo?a= will
# yeild $a == 56 here.
}
location /bar {
set $foo "hello\n\n'\"\\";
set_quote_sql_str $foo $foo; # for mysql
# OR in-place editing:
# set_quote_sql_str $foo;
# now $foo is: 'hello\n\n\'\"\\'
}
location /bar {
set $foo "hello\n\n'\"\\";
set_quote_pgsql_str $foo; # for PostgreSQL
# now $foo is: E'hello\n\n\'\"\\'
}
location /json {
set $foo "hello\n\n'\"\\";
set_quote_json_str $foo $foo;
# OR in-place editing:
# set_quote_json_str $foo;
# now $foo is: "hello\n\n'\"\\"
}
location /baz {
set $foo "hello%20world";
set_unescape_uri $foo $foo;
# OR in-place editing:
# set_unescape_uri $foo;
# now $foo is: hello world
}
upstream_list universe moon sun earth;
upstream moon { ... }
upstream sun { ... }
upstream earth { ... }
location /foo {
set_hashed_upstream $backend universe $arg_id;
drizzle_pass $backend; # used with ngx_drizzle
}
location /base32 {
set $a 'abcde';
set_encode_base32 $a;
set_decode_base32 $b $a;
# now $a == 'c5h66p35' and
# $b == 'abcde'
}
location /base64 {
set $a 'abcde';
set_encode_base64 $a;
set_decode_base64 $b $a;
# now $a == 'YWJjZGU=' and
# $b == 'abcde'
}
location /hex {
set $a 'abcde';
set_encode_hex $a;
set_decode_hex $b $a;
# now $a == '6162636465' and
# $b == 'abcde'
}
# GET /sha1 yields the output
# aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d
location /sha1 {
set_sha1 $a hello;
echo $a;
}
# ditto
location /sha1 {
set $a hello;
set_sha1 $a;
echo $a;
}
# GET /today yields the date of today in local time using format 'yyyy-mm-dd'
location /today {
set_local_today $today;
echo $today;
}
# GET /signature yields the hmac-sha-1 signature
# given a secret and a string to sign
# this example yields the base64 encoded singature which is
# "HkADYytcoQQzqbjQX33k/ZBB/DQ="
location /signature {
set $secret_key 'secret-key';
set $string_to_sign "some-string-to-sign";
set_hmac_sha1 $signature $secret_key $string_to_sign;
set_encode_base64 $signature $signature;
echo $signature;
}
location = /rand {
set $from 3;
set $to 15;
set_random $rand $from $to;
# or write directly
# set_random $rand 3 15;
echo $rand; # will print a random integer in the range [3, 15]
}
Description
This module extends the standard HttpRewriteModule's directive set to
provide more functionalities like URI escaping and unescaping, JSON
quoting, Hexadecimal/MD5/SHA1/Base32/Base64 digest encoding and
decoding, random number generator, and more!
Every directive provided by this module can be mixed freely with other
[[HttpRewriteModule]]'s directives, like if and set. (Thanks to the
Nginx Devel Kit (<https://github.com/simpl/ngx_devel_kit>)!)
Directives
set_if_empty
syntax: *set_if_empty $dst <src>*
default: *no*
context: *location, location if*
phase: *rewrite*
Assign the value of the argument "<src>" if and only if variable $dst is
empty (i.e., not found or has an empty string value).
In the following example,
set $a 32;
set_if_empty $a 56;
the variable $dst will take the value 32 at last. But in the sample
set $a '';
set $value "hello, world"
set_if_empty $a $value;
$a will take the value "hello, world" at last.
set_quote_sql_str
syntax: *set_quote_sql_str $dst <src>*
syntax: *set_quote_sql_str $dst*
default: *no*
context: *location, location if*
phase: *rewrite*
category: *ndk_set_var_value*
When taking two arguments, this directive will quote the value of the
second argument "<src>" by MySQL's string value quoting rule and assign
the result into the first argument, variable $dst. For example,
location /test {
set $value "hello\n\r'\"\\";
set_quote_sql_str $quoted $value;
echo $quoted;
}
Then request "GET /test" will yield the following output
'hello\n\r\'\"\\'
Please note that we're using [[HttpEchoModule]]'s [directive
(HttpEchoModule#echo)] here to output values of nginx variables
directly.
When taking a single argument, this directive will do in-place
modification of the argument variable. For example,
location /test {
set $value "hello\n\r'\"\\";
set_quote_sql_str $value;
echo $value;
}
then request "GET /test" will give exactly the same output as the
previous example.
This directive is usually used to prevent SQL injection.
This directive can be invoked by [[HttpLuaModule]]'s
ndk.set_var.DIRECTIVE interface and [[HttpArrayVarModule]]'s
array_map_op directive.
set_quote_pgsql_str
syntax: *set_quote_pgsql_str $dst <src>*
syntax: *set_quote_pgsql_str $dst*
default: *no*
context: *location, location if*
phase: *rewrite*
category: *ndk_set_var_value*
Very much like set_quote_sql_str, but with PostgreSQL quoting rules for
SQL string literals.
set_quote_json_str
syntax: *set_quote_json_str $dst <src>*
syntax: *set_quote_json_str $dst*
default: *no*
context: *location, location if*
phase: *rewrite*
category: *ndk_set_var_value*
When taking two arguments, this directive will quote the value of the
second argument "<src>" by JSON string value quoting rule and assign the
result into the first argument, variable $dst. For example,
location /test {
set $value "hello\n\r'\"\\";
set_quote_json_str $quoted $value;
echo $quoted;
}
Then request "GET /test" will yield the following output
"hello\n\r'\"\\"
Please note that we're using [[HttpEchoModule]]'s [directive
(HttpEchoModule#echo)] here to output values of nginx variables
directly.
When taking a single argument, this directive will do in-place
modification of the argument variable. For example,
location /test {
set $value "hello\n\r'\"\\";
set_quote_json_str $value;
echo $value;
}
then request "GET /test" will give exactly the same output as the
previous example.
This directive can be invoked by [[HttpLuaModule]]'s
ndk.set_var.DIRECTIVE interface and [[HttpArrayVarModule]]'s
array_map_op directive.
set_unescape_uri
syntax: *set_unescape_uri $dst <src>*
syntax: *set_unescape_uri $dst*
default: *no*
context: *location, location if*
phase: *rewrite*
category: *ndk_set_var_value*
When taking two arguments, this directive will unescape the value of the
second argument "<src>" as a URI component and assign the result into
the first argument, variable $dst. For example,
location /test {
set_unescape_uri $key $arg_key;
echo $key;
}
Then request "GET /test?key=hello+world%21" will yield the following
output
hello world!
The nginx standard $arg_PARAMETER variable holds the raw (escaped) value
of the URI parameter. So we need the "set_unescape_uri" directive to
unescape it first.
Please note that we're using [[HttpEchoModule]]'s [directive
(HttpEchoModule#echo)] here to output values of nginx variables
directly.
When taking a single argument, this directive will do in-place
modification of the argument variable. For example,
location /test {
set $key $arg_key;
set_unescape_uri $key;
echo $key;
}
then request "GET /test?key=hello+world%21" will give exactly the same
output as the previous example.
This directive can be invoked by [[HttpLuaModule]]'s
ndk.set_var.DIRECTIVE interface and [[HttpArrayVarModule]]'s
array_map_op directive.
set_escape_uri
syntax: *set_escape_uri $dst <src>*
syntax: *set_escape_uri $dst*
default: *no*
context: *location, location if*
phase: *rewrite*
category: *ndk_set_var_value*
Very much like the set_unescape_uri directive, but does the conversion
the other way around, i.e., URL component escaping.
set_hashed_upstream
syntax: *set_hashed_upstream $dst <upstream_list_name> <src>*
default: *no*
context: *location, location if*
phase: *rewrite*
Hashes the string argument "<src>" into one of the upstream name
included in the upstream list named "<upstream_list_name>". The hash
function being used is simple modulo.
Here's an example,
upstream moon { ... }
upstream sun { ... }
upstream earth { ... }
upstream_list universe moon sun earth;
location /test {
set_unescape_uri $key $arg_key;
set $list_name universe;
set_hashed_upstream $backend $list_name $key;
echo $backend;
}
Then "GET /test?key=blah" will output either "moon", "sun", or "earth",
depending on the actual value of the "key" query argument.
This directive is usually used to compute an nginx variable to be passed
to [[HttpMemcModule]]'s memc_pass directive, [[HttpRedis2Module]]'s
[[HttpRedis2Module#redis2_pass]] directive, and [[HttpProxyModule]]'s
proxy_pass directive, among others.
set_encode_base32
syntax: *set_encode_base32 $dst <src>*
syntax: *set_encode_base32 $dst*
default: *no*
context: *location, location if*
phase: *rewrite*
category: *ndk_set_var_value*
When taking two arguments, this directive will encode the value of the
second argument "<src>" to its base32(hex) digest and assign the result
into the first argument, variable $dst. For example,
location /test {
set $raw "abcde";
set_encode_base32 $digest $raw;
echo $digest;
}
Then request "GET /test" will yield the following output
c5h66p35
Please note that we're using [[HttpEchoModule]]'s [directive
(HttpEchoModule#echo)] here to output values of nginx variables
directly.
RFC forces the "[A-Z2-7]" RFC-3548 compliant encoding, but we're using
the "base32hex" encoding ("[0-9a-v]").
By default, the "=" character is used to pad the left-over bytes due to
alignment. But the padding behavior can be completely disabled by
setting set_misc_base32_padding "off".
When taking a single argument, this directive will do in-place
modification of the argument variable. For example,
location /test {
set $value "abcde";
set_encode_base32 $value;
echo $value;
}
then request "GET /test" will give exactly the same output as the
previous example.
This directive can be invoked by [[HttpLuaModule]]'s
ndk.set_var.DIRECTIVE interface and [[HttpArrayVarModule]]'s
array_map_op directive.
set_misc_base32_padding
syntax: *set_misc_base32_padding on|off*
default: *on*
context: *http, server, server if, location, location if*
phase: *no*
This directive can control whether to pad left-over bytes with the "="
character when encoding a base32 digest by the set_encode_base32
directive.
set_decode_base32
syntax: *set_decode_base32 $dst <src>*
syntax: *set_decode_base32 $dst*
default: *no*
context: *location, location if*
phase: *rewrite*
category: *ndk_set_var_value*
Similar to the set_encode_base32 directive, but does exactly the the
opposite operation, .i.e, decoding a base32(hex) digest into its
original form.
set_encode_base64
syntax: *set_encode_base64 $dst <src>*
syntax: *set_encode_base64 $dst*
default: *no*
context: *location, location if*
phase: *rewrite*
category: *ndk_set_var_value*
When taking two arguments, this directive will encode the value of the
second argument "<src>" to its base64 digest and assign the result into
the first argument, variable $dst. For example,
location /test {
set $raw "abcde";
set_encode_base64 $digest $raw;
echo $digest;
}
Then request "GET /test" will yield the following output
YWJjZGU=
Please note that we're using [[HttpEchoModule]]'s [directive
(HttpEchoModule#echo)] here to output values of nginx variables
directly.
When taking a single argument, this directive will do in-place
modification of the argument variable. For example,
location /test {
set $value "abcde";
set_encode_base64 $value;
echo $value;
}
then request "GET /test" will give exactly the same output as the
previous example.
This directive can be invoked by [[HttpLuaModule]]'s
ndk.set_var.DIRECTIVE interface and [[HttpArrayVarModule]]'s
array_map_op directive.
set_decode_base64
syntax: *set_decode_base64 $dst <src>*
syntax: *set_decode_base64 $dst*
default: *no*
context: *location, location if*
phase: *rewrite*
category: *ndk_set_var_value*
Similar to the set_encode_base64 directive, but does exactly the the
opposite operation, .i.e, decoding a base64 digest into its original
form.
set_encode_hex
syntax: *set_encode_hex $dst <src>*
syntax: *set_encode_hex $dst*
default: *no*
context: *location, location if*
phase: *rewrite*
category: *ndk_set_var_value*
When taking two arguments, this directive will encode the value of the
second argument "<src>" to its hexadecimal digest and assign the result
into the first argument, variable $dst. For example,
location /test {
set $raw "章亦春";
set_encode_hex $digest $raw;
echo $digest;
}
Then request "GET /test" will yield the following output
e7aba0e4baa6e698a5
Please note that we're using [[HttpEchoModule]]'s [directive
(HttpEchoModule#echo)] here to output values of nginx variables
directly.
When taking a single argument, this directive will do in-place
modification of the argument variable. For example,
location /test {
set $value "章亦春";
set_encode_hex $value;
echo $value;
}
then request "GET /test" will give exactly the same output as the
previous example.
This directive can be invoked by [[HttpLuaModule]]'s
ndk.set_var.DIRECTIVE interface and [[HttpArrayVarModule]]'s
array_map_op directive.
set_decode_hex
syntax: *set_decode_hex $dst <src>*
syntax: *set_decode_hex $dst*
default: *no*
context: *location, location if*
phase: *rewrite*
category: *ndk_set_var_value*
Similar to the set_encode_hex directive, but does exactly the the
opposite operation, .i.e, decoding a hexadecimal digest into its
original form.
set_sha1
syntax: *set_sha1 $dst <src>*
syntax: *set_sha1 $dst*
default: *no*
context: *location, location if*
phase: *rewrite*
category: *ndk_set_var_value*
When taking two arguments, this directive will encode the value of the
second argument "<src>" to its SHA-1
(<http://en.wikipedia.org/wiki/SHA-1>) digest and assign the result into
the first argument, variable $dst. The hexadecimal form of the "SHA-1"
digest will be generated automatically, use set_decode_hex to decode the
result if you want the binary form of the "SHA-1" digest.
For example,
location /test {
set $raw "hello";
set_sha1 $digest $raw;
echo $digest;
}
Then request "GET /test" will yield the following output
aaf4c61ddcc5e8a2dabede0f3b482cd9aea9434d
Please note that we're using [[HttpEchoModule]]'s [directive
(HttpEchoModule#echo)] here to output values of nginx variables
directly.
When taking a single argument, this directive will do in-place
modification of the argument variable. For example,
location /test {
set $value "hello";
set_sha1 $value;
echo $value;
}
then request "GET /test" will give exactly the same output as the
previous example.
This directive can be invoked by [[HttpLuaModule]]'s
ndk.set_var.DIRECTIVE interface and [[HttpArrayVarModule]]'s
array_map_op directive.
set_md5
syntax: *set_md5 $dst <src>*
syntax: *set_md5 $dst*
default: *no*
context: *location, location if*
phase: *rewrite*
category: *ndk_set_var_value*
When taking two arguments, this directive will encode the value of the
second argument "<src>" to its MD5 (<http://en.wikipedia.org/wiki/MD5>)
digest and assign the result into the first argument, variable $dst. The
hexadecimal form of the "MD5" digest will be generated automatically,
use set_decode_hex to decode the result if you want the binary form of
the "MD5" digest.
For example,
location /test {
set $raw "hello";
set_md5 $digest $raw;
echo $digest;
}
Then request "GET /test" will yield the following output
5d41402abc4b2a76b9719d911017c592
Please note that we're using [[HttpEchoModule]]'s [directive
(HttpEchoModule#echo)] here to output values of nginx variables
directly.
When taking a single argument, this directive will do in-place
modification of the argument variable. For example,
location /test {
set $value "hello";
set_md5 $value;
echo $value;
}
then request "GET /test" will give exactly the same output as the
previous example.
This directive can be invoked by [[HttpLuaModule]]'s
ndk.set_var.DIRECTIVE interface and [[HttpArrayVarModule]]'s
array_map_op directive.
set_hmac_sha1
syntax: *set_hmac_sha1 $dst <secret_key> <src>*
syntax: *set_hmac_sha1 $dst*
default: *no*
context: *location, location if*
phase: *rewrite*
Computes the HMAC-SHA1 (<http://en.wikipedia.org/wiki/HMAC>) digest of
the argument "<src>" and assigns the result into the argument variable
$dst with the secret key "<secret_key>".
The raw binary form of the "HMAC-SHA1" digest will be generated, use
set_encode_base64, for example, to encode the result to a textual
representation if desired.
For example,
location /test {
set $secret 'thisisverysecretstuff';
set $string_to_sign 'some string we want to sign';
set_hmac_sha1 $signature $secret $string_to_sign;
set_encode_base64 $signature $signature;
echo $signature;
}
Then request "GET /test" will yield the following output
R/pvxzHC4NLtj7S+kXFg/NePTmk=
Please note that we're using [[HttpEchoModule]]'s [directive
(HttpEchoModule#echo)] here to output values of nginx variables
directly.
This directive requires the OpenSSL library enabled in your Nignx build
(usually by passing the "--with-http_ssl_module" option to the
"./configure" script).
set_random
syntax: *set_random $res <from> <to>*
default: *no*
context: *location, location if*
phase: *rewrite*
Generates a (pseudo) random number (in textual form) within the range
"[<$from>, <$to>]" (inclusive).
Only non-negative numbers are allowed for the "<from>" and "<to>"
arguments.
When "<from>" is greater than "<to>", their values will be exchanged
accordingly.
For instance,
location /test {
set $from 5;
set $to 7;
set_random $res $from $to;
echo $res;
}
then request "GET /test" will output a number between 5 and 7 (i.e.,
among 5, 6, 7).
For now, there's no way to configure a custom random generator seed.
Behind the scene, it makes use of the standard C function "rand()".
This directive was first introduced in the "v0.22rc1" release.
See also set_secure_random_alphanum and set_secure_random_lcalpha.
set_secure_random_alphanum
syntax: *set_secure_random_alphanum $res <length>*
default: *no*
context: *location, location if*
phase: *rewrite*
Generates a cryptographically-strong random string "<length>" characters
long with the alphabet "[a-zA-Z0-9]".
"<length>" may be between 1 and 64, inclusive.
For instance,
location /test {
set_secure_random_alphanum $res 32;
echo $res;
}
then request "GET /test" will output a string like
"ivVVRP2DGaAqDmdf3Rv4ZDJ7k0gOfASz".
This function depends on the presence of the "/dev/urandom" device,
available on most UNIX-like systems.
See also set_secure_random_lcalpha and set_random.
This directive was first introduced in the "v0.22rc8" release.
set_secure_random_lcalpha
syntax: *set_secure_random_lcalpha $res <length>*
default: *no*
context: *location, location if*
phase: *rewrite*
Generates a cryptographically-strong random string "<length>" characters
long with the alphabet "[a-z]".
"<length>" may be between 1 and 64, inclusive.
For instance,
location /test {
set_secure_random_lcalpha $res 32;
echo $res;
}
then request "GET /test" will output a string like
"kcuxcddktffsippuekhshdaclaquiusj".
This function depends on the presence of the "/dev/urandom" device,
available on most UNIX-like systems.
This directive was first introduced in the "v0.22rc8" release.
See also set_secure_random_alphanum and set_random.
set_rotate
syntax: *set_rotate $value <from> <to>*
default: *no*
context: *location, location if*
phase: *rewrite*
Increments $value but keeps it in range from "<from>" to "<to>". If
$value is greater than "<to>" or less than "<from>" is will be set to
"<from>" value.
The current value after running this directive will always be saved on a
per-location basis. And the this saved value will be used for
incrementation when the $value is not initialized or has a bad value.
Only non-negative numbers are allowed for the "<from>" and "<to>"
arguments.
When "<from>" is greater than "<to>", their values will be exchanged
accordingly.
For instance,
location /rotate {
default_type text/plain;
set $counter $cookie_counter;
set_rotate $counter 1 5;
echo $counter;
add_header Set-Cookie counter=$counter;
}
then request "GET /rotate" will output next number between 1 and 5
(i.e., 1, 2, 3, 4, 5) on each refresh of the page. This directive may be
userful for banner rotation purposes.
Another example is to use server-side value persistence to do simple
round-robin:
location /rotate {
default_type text/plain;
set_rotate $counter 0 3;
echo $counter;
}
And accessing "/rotate" will also output integer sequence 0, 1, 2, 3, 0,
1, 2, 3, and so on.
This directive was first introduced in the "v0.22rc7" release.
set_local_today
syntax: *set_local_today $dst*
default: *no*
context: *location, location if*
phase: *rewrite*
Set today's date ("yyyy-mm-dd") in localtime to the argument variable
$dst.
Here's an example,
location /today {
set_local_today $today;
echo $today;
}
then request "GET /today" will output something like
2011-08-16
and year, the actual date you get here will vary every day ;)
Behind the scene, this directive utilizes the "ngx_time" API in the
Nginx core, so usually no syscall is involved due to the time caching
mechanism in the Nginx core.
Caveats
Do not use $arg_PARAMETER, $cookie_COOKIE, $http_HEADER or other special
variables defined in the Nginx core module as the target variable in
this module's directives. For instance,
set_if_empty $arg_user 'foo'; # DO NOT USE THIS!
may lead to segmentation faults.
Installation
Grab the nginx source code from nginx.org (<http://nginx.org/>), for
example, the version 1.0.15 (see nginx compatibility), and then build
the source with this module:
wget 'http://nginx.org/download/nginx-1.0.15.tar.gz'
tar -xzvf nginx-1.0.15.tar.gz
cd nginx-1.0.15/
# Here we assume you would install you nginx under /opt/nginx/.
./configure --prefix=/opt/nginx \
--with-http_ssl_module \
--add-module=/path/to/ngx_devel_kit \
--add-module=/path/to/set-misc-nginx-module
make -j2
make install
Download the latest version of the release tarball of this module from
set-misc-nginx-module file list
(<http://github.com/agentzh/set-misc-nginx-module/tags>), and the latest
tarball for ngx_devel_kit (<https://github.com/simpl/ngx_devel_kit>)
from its file list (<https://github.com/simpl/ngx_devel_kit/tags>).
Also, this module is included and enabled by default in the
ngx_openresty bundle (<http://openresty.org/>).
Compatibility
The following versions of Nginx should work with this module:
* 1.1.x (last tested: 1.1.5)
* 1.0.x (last tested: 1.0.15)
* 0.9.x (last tested: 0.9.4)
* 0.8.x (last tested: 0.8.54)
* 0.7.x >= 0.7.46 (last tested: 0.7.68)
If you find that any particular version of Nginx above 0.7.46 does not
work with this module, please consider reporting a bug.
Report Bugs
Although a lot of effort has been put into testing and code tuning,
there must be some serious bugs lurking somewhere in this module. So