core-file-count <core-file-count_int>

The maximum core dump file number. The valid values are 3 and 5.

enable-core-file {enable | disable | enable-best-effort}

disable: Disable coredump for proxyd.

enable: Enable coredump action for proxyd. It will stop if coredump cannot finish in hung task timeout seconds.

enable-best-effort: Enable coredump action for proxy. It will stop until the entire core file is generated. This option is useful to analyze a tough issue, though it may cause your service to stop responding for a long time

enable-session-statistics {enable | disable}

enable-single-worker {enable | disable}

hsm {enable | disable}

no-session-limit {enable | disable}

Enable not to limit the maximum concurrency sessions of FortiWeb-VM.

If this option is disabled, the maximum concurrent sessions for all the policies on a VM is 20,000 (2vCPUs), 50,000 (4vCPUs), or 100,000 (8vCPUs); For each policy, the number is 8,000 (2vCPUs), 15,000 (4vCPUs), or 50,000 (8vCPUs).

no-ssl-encrypt-then-mac {enable | disable}

use-first-ack-mac {enable | disable}

dpdk {enable | disable}

high-compatibility-mode {enable | disable}

Enable to accelerate SSL transport.

The setting works on certain hardware platforms which have SSL accelerate card. When enabled, the SSL accelerate card will do SSL traffic acceleration for SSL encryption and decryption.

offline-session-timeout {seconds_int}

This setting only works in Offline Protection mode.

It's a session optimization option. FortiWeb's resources will be unnecessarily consumed if the connection always keeps on. With this option, you can configure the session timeout value to avoid them staying on for too long.

The valid range is seconds 30–1200 seconds.

If enabled, the reason of the content routing failure will be recorded in event log.

server-invalid-no-reponse {enable | disable}

Enable this option so that closes the client connection when all the servers in the server pool are unresponsive.

using-dns-proxy {enable | disable}

This option is enabled by default. If it is disabled, the system uses getaddrinfo to resolve the domain name.

df-flag {enable | disable}

Enable to allow FortiWeb to send non DF-flag packet to pass the device with low MTU.

tls12-compatible-sigalg {enable | disable}

When tls12-compatible-sigalg is enabled, signature algorithm negotiation in TLS handshake for FortiWeb behaves exactly the same as OpenSSL 1.1.0.

Please note executing this command causes the proxyd to restart so all current sessions will be dropped.

This command is specific to very rare case. Do not use it unless suggested by Fortinet support team.

corefile-ha-failover {enable | disable}

Enable to trigger HA fail-over upon proxyd coredump, so that the secondary node can immediately take over the traffic when coredump file is being generated on the primary node.

Note the following when using this command:

• You should set enable-core-file to enable or enable-best-effort for the corefile-ha-failover to work.

• The enable-core-file and corefile-ha-failover attributes will NOT be synchronized to other devices in the same HA group, so you need to configure these configurations on each device if needed.

• Currently only the proxyd daemon coredump can trigger corefile-ha-failover. Other daemons can't trigger it.

• This function works in active-passive and active-active standard HA modes. It is not suggested to enable it in HA Manager mode on public clouds, because usually the load balancer in front of the FortiWeb devices will do health check and guarantee that traffic is dispatched to the healthy nodes.

• It is recommended to enable this option only on one FortiWeb, usually the primary device. Otherwise a proxyd coredump occurring on both devices may lead to HA fail-over back and forth between two devices.