[Nginx] Compare rewrite last break

syntax

rewrite regex replacement [ flag ]

  • last – completes processing of current rewrite directives and restarts the process (including rewriting) with a search for a match on the URI from all available locations.
  • break – completes processing of current rewrite directives and non-rewrite processing continues within the current location block only.
  • redirect – returns temporary redirect with code 302; it is used if the substituting line begins with http:// (デフォルト)
  • permanent – returns permanent redirect with code 301

break last

/etc/nginx/conf.d/default.conf


root   /usr/share/nginx/html;
rewrite_log on;
 
location /rewrite {
    rewrite ^/rewrite  /foo;
    rewrite ^/foo      /bar;
    add_header H-rewrite dummy;
}
 
location /last {
    rewrite ^/last     /foo last;
    rewrite ^/foo      /bar last;
    add_header H-last dummy;
}
 
location /break {
    rewrite ^/break    /foo break;
    rewrite ^/foo      /bar break;
    add_header H-break dummy;
}
 
location /foo {
    add_header H-foo dummy;
}
 
location /bar {
    add_header H-bar dummy;
}
 
location / {
    index  index.html index.htm;
    add_header H-index dummy;
}


# echo foo > /usr/share/nginx/html/foo
# echo bar > /usr/share/nginx/html/bar

Test rewrite


$ curl -D - http://localhost/rewrite
HTTP/1.1 200 OK
Server: nginx/1.4.4
Date: Sun, 16 Feb 2014 06:05:42 GMT
Content-Type: application/octet-stream
Content-Length: 4
Last-Modified: Sat, 15 Feb 2014 15:12:05 GMT
Connection: keep-alive
ETag: "52ff83c5-4"
H-bar: dummy
Accept-Ranges: bytes
 
bar

nginx log


2014/02/16 15:05:42 [notice] 21738#0: *4 "^/rewrite" matches "/rewrite", client: 127.0.0.1, server: localhost, request: "GET /rewrite HTTP/1.1", host: "localhost"
2014/02/16 15:05:42 [notice] 21738#0: *4 rewritten data: "/foo", args: "", client: 127.0.0.1, server: localhost, request: "GET /rewrite HTTP/1.1", host: "localhost"
2014/02/16 15:05:42 [notice] 21738#0: *4 "^/foo" matches "/foo", client: 127.0.0.1, server: localhost, request: "GET /rewrite HTTP/1.1", host: "localhost"
2014/02/16 15:05:42 [notice] 21738#0: *4 rewritten data: "/bar", args:

Test break rewrite


$ curl -D - http://localhost/break
HTTP/1.1 200 OK
Server: nginx/1.4.4
Date: Sun, 16 Feb 2014 06:06:14 GMT
Content-Type: application/octet-stream
Content-Length: 4
Last-Modified: Sat, 15 Feb 2014 15:12:01 GMT
Connection: keep-alive
ETag: "52ff83c1-4"
H-break: dummy
Accept-Ranges: bytes
 
foo

nginx log


2014/02/16 15:06:14 [notice] 21738#0: *5 "^/break" matches "/break", client: 127.0.0.1, server: localhost, request: "GET /break HTTP/1.1", host: "localhost"
2014/02/16 15:06:14 [notice] 21738#0: *5 rewritten data: "/foo", args: "", client: 127.0.0.1, server: localhost, request: "GET /break HTTP/1.1", host: "localhost"

Test last rewrite


$ curl -D - http://localhost/last
HTTP/1.1 200 OK
Server: nginx/1.4.4
Date: Sun, 16 Feb 2014 06:06:38 GMT
Content-Type: application/octet-stream
Content-Length: 4
Last-Modified: Sat, 15 Feb 2014 15:12:01 GMT
Connection: keep-alive
ETag: "52ff83c1-4"
H-foo: dummy
Accept-Ranges: bytes
 
foo

nginx log


2014/02/16 15:06:38 [notice] 21738#0: *6 "^/last" matches "/last", client: 127.0.0.1, server: localhost, request: "GET /last HTTP/1.1", host: "localhost"
2014/02/16 15:06:38 [notice] 21738#0: *6 rewritten data: "/foo", args: "", client: 127.0.0.1, server: localhost, request: "GET /last HTTP/1.1", host: "localhost"

References

Nhận xét

Đăng nhận xét

Bài đăng phổ biến từ blog này

CLEANING UP THE ZABBIX DATABASE

My Zabbix database size increased a lot in the last few months and since my disk was running out space, I decided to clean up the old events from the database. Looking at the database tables, the biggest one was  history_uint , which holds the items history data – over 400 millions of records and over 30 Gb of disk space before the clean up. Since deleting the old records from this table directly would be a very slow process, I decided to create a new table and insert the latest records from the  history_uint  table and then just replace the old table with a new one. Since this is not an offical procedure, use it at your own risk. Environment: Zabbix v2.2 MySql 5.1 – InnoDB with  innodb_file_per_table=ON Step 1 – Stop the Zabbix server Step 2 – Open your favourite MySQL client and create a new table CREATE TABLE  history_uint_new  LIKE  history_uint; Step 3 – Insert the latest records from the  history_uint  table to the  history_uint_new table First you need to de
Đọc thêm

Configuring DHCP Relay service on the FortiGate unit

Configuring DHCP Relay service on the FortiGate unit If the clients are configured to obtain a IP address using DHCP relay, configure the FortiGate server as below: To configure DHCP relay on the FortiGate unit   1. Go to System > Network > Interfaces and select Interface want to configure DHCP relay.   2. Enable DHCP Server in the interface and choose Advanced   3. For Mode, select Relay.   4. In Type select Regular.   5. Select OK.   6. If a router is installed between the FortiGate unit and the DHCP server, define a static route to the DHCP server. Note : Sometimes it is required to specify more than one DHCP relay IP, to allow for the coverage of additional LAN subnets. Although the Web Based Manager (GUI) does not provide an option to configure this, it is possible to set up to 8 IPs from the CLI.       config system interface             edit <REQUIRED_INTERFACE_HERE>               set dhcp-relay-ip <FIRST_IP> <SECOND_IP> ....<EIGHTH_IP&
Đọc thêm

Stuxnet Trojan - Memory Forensics with Volatility | Part I

Hình ảnh
Stuxnet could be the first advanced malware. It is thought that it was developed by the United States and Israel to attack Iran's nuclear facilities. It attacked Windows systems using a zero-day exploit and It was focused on SCADA systems in order to  affect critical infrastructures... Also, it may be spread from USB drivers. It is necessary a squad of highly capable programmers with depth of knowledge of industrial processes and an interest in attacking industrial infrastructure to develop this malware. Kaspersky Lab concluded that the sophisticated attack could only have been conducted "with nation-state support" and a study of the spread of Stuxnet by Symantec says that it was spread to Iran (58.85%), Indonesia (18.22%), India (8.31%), Azerbaijan (2.57%).... Thanks to Malware Cookbook we can download a memory dump from an infected host with this malware in the URL below:  http://www.jonrajewski.com/data/Malware/stuxnet.vmem.zip Ok, let’s go. We are going to analyze i
Đọc thêm