Fortinet Document Library

Version:

Version:

Version:

Version:

Version:

Version:

Version:


Table of Contents

CLI Reference

config load-balance pagespeed

Use this command to set which kind of HTTP requests will be handled by PageSpeed and how to accelerate.

Syntax

config load-balance pagespeed

edit <name>

set file-cache-inode-limit <1-100000>

set file-cache-size-limit <1-512>

set profile <datasource>

 

config page-control

edit <id>

set type include/exclude

set uri-pattern <uri regex>

next

end

 

config resource-control

edit <id>

set fetch-domain <string>

set origin-domain-pattern <regex string>

set rewrite-domain <string>

next

end

end

Parameter Description
file-cache-inode-limit The maximum file cache inode.
file-cache-size-limit The maximum file cache size (1M ~512M).
profile The name of the PageSpeed profile.
config page-control  
Type The include/exclude type.
full-uri-pattern

The full URI regex, such as http(s)://*example.com/*/htmls/*.html.

Note: Wildcards include * which matches any 0 or more characters, and ?, which matches exactly one character. Unlike Unix shells, the / directory separator is not special, and can be matched by either * or ?. The resources are always expanded into their absolute form before expanding.

Config resource-control  
origin-domain-pattern The origin domain regex, such as (http(s)://)*.example.com.
fetch-domain The fetch domain string, such as http://www.example.com.
rewrite-domain

The rewrite domain string, such as http://www.example.com.

Note: In the HTTP response body, the HTML sometimes links with certain resource URL. If the resource contain a domain name, FortiADC will perform the activity according to the fetch-domain setting or the rewrite-domain setting.

Example:

config load-balance pagespeed

edit "all"

set profile all

set file-cache-inode-limit 10000

set file-cache-size-limit 128

config page-control

edit 1

set type include

set uri-pattern *

next

end

config resource-control

end

next

end

config load-balance pagespeed

Use this command to set which kind of HTTP requests will be handled by PageSpeed and how to accelerate.

Syntax

config load-balance pagespeed

edit <name>

set file-cache-inode-limit <1-100000>

set file-cache-size-limit <1-512>

set profile <datasource>

 

config page-control

edit <id>

set type include/exclude

set uri-pattern <uri regex>

next

end

 

config resource-control

edit <id>

set fetch-domain <string>

set origin-domain-pattern <regex string>

set rewrite-domain <string>

next

end

end

Parameter Description
file-cache-inode-limit The maximum file cache inode.
file-cache-size-limit The maximum file cache size (1M ~512M).
profile The name of the PageSpeed profile.
config page-control  
Type The include/exclude type.
full-uri-pattern

The full URI regex, such as http(s)://*example.com/*/htmls/*.html.

Note: Wildcards include * which matches any 0 or more characters, and ?, which matches exactly one character. Unlike Unix shells, the / directory separator is not special, and can be matched by either * or ?. The resources are always expanded into their absolute form before expanding.

Config resource-control  
origin-domain-pattern The origin domain regex, such as (http(s)://)*.example.com.
fetch-domain The fetch domain string, such as http://www.example.com.
rewrite-domain

The rewrite domain string, such as http://www.example.com.

Note: In the HTTP response body, the HTML sometimes links with certain resource URL. If the resource contain a domain name, FortiADC will perform the activity according to the fetch-domain setting or the rewrite-domain setting.

Example:

config load-balance pagespeed

edit "all"

set profile all

set file-cache-inode-limit 10000

set file-cache-size-limit 128

config page-control

edit 1

set type include

set uri-pattern *

next

end

config resource-control

end

next

end