Is it right to use the default profiles as they are in production?

Short answer

It is safe as a starting point, but leaving them in production without reviewing them is not recommended. The built-in defaults (Default Profile in the selector, Stream Log for logs) are set according to a general scenario: the Compression default compresses only text/plain content with Compression Level 1, in the Timeouts default the Server Timeout and Client Timeout are 90 seconds, and the vService Limits default limits concurrent connections to 20,000. These profiles do not appear on the list screen and cannot be edited; if an application-specific value is needed, a new profile is created and assigned to the vService. There is no default profile for Trusted Proxies and Health Checks; if none is assigned, the real client IP is not resolved from the header and no health check is performed.

How Does It Work?

1. When a profile box (e.g. Compression, Timeout) is checked in the Details panel of the vService form, the built-in default comes first in the selector: Default Profile for profiles, and Stream Log or the first defined log profile in the LOG box.
2. Even if the Timeout and vService Limits boxes are not checked, the built-in default values are applied; timeouts and limits are never "unlimited".
3. The built-in defaults are not included in the profile list and cannot be edited. A different value is applied by assigning to the vService a new profile created with Add on the same screen.
4. There is no built-in profile for Trusted Proxies and Health Checks: the selector of the Trusted Proxy box has no default option; if no health check is assigned to the Backend Service, the server is always considered up.

Defaults and When to Change Them

Profile	Built-in default	When it should be changed	Details
Compression	GZIP, only text/plain, Compression Level 1	If HTML, CSS, JS or JSON is to be compressed	How is compression (GZIP / DEFLATE) enabled; which content types should be compressed?
Cache	Common static file extensions, 1 hour	If the content to be cached or the duration is different	Can I do caching on TR7; what are the default settings?
Timeouts	HTTP Request Timeout 30 s, Connect Timeout 20 s, Server Timeout 90 s, Client Timeout 90 s, Queue Timeout 60 s, Tunnel(Websocket) Timeout 120 s	If there are long-running operations or WebSocket	Why is the request cut off during long operations (report, file upload); which timeout should I increase?
vService Limits	Max. Total Connections 20,000, Max. Failed Connection Retries 3, Buffer Size(kB) 128	If there is high concurrency, large headers or large content pages	What is the vService Limits profile; what are the default limits?
Logs	Stream Log: records are kept only on the device and are not sent out	If logs are to be sent to a SIEM	How do I send logs to a SIEM (Syslog)?
Notifications	Backend Service and vService status notification on, thresholds defined; no e-mail, SMS or messaging recipient	If notifications are to be received	Can I get notified when a vService goes down; which channels are available (SNMP, e-mail, SMS)?
TLS Security Profiles	Minimum TLS 1.1, only secure ciphers	If TLS 1.1 is to be turned off or the cipher list is to be narrowed	What is a TLS Security Profile, and what does it configure?
Trusted Proxies	None	If there is a CDN or proxy in front of TR7	There is a CDN such as Cloudflare / Akamai in front of TR7; how do I get the Real client IP (trusted proxy)?
Health Checks	None; no health check is assigned on the Backend Service	For every Backend Service	What does a Health Check do; what happens if I don't assign one?

Default Profiles in TR7

To use a custom profile instead of the default, a new profile is created with Add on the profile screen (Configuration Menu → Load Balancer → Profiles (L4-L7 Behavior Sets)) and selected in the related box in the Details panel of the vService form. Which vService uses which profile is read in the Load Balancer Management tab on the vService screen; rows that use a built-in default have no edit pencil, and only the quick view opens. Before a shared profile is changed, its impact is checked from the Used in tab (How do I understand the impact of changing a profile before I change it ("Used in")?).

Common Misconceptions

• "If the Timeout box is not checked, there is no timeout." Even if no profile is selected, the built-in default values apply.
• "The Default Profile can be edited to change all vServices at the same time." The built-in default cannot be edited; a new profile is created and assigned to the vServices.
• "When Compression is turned on, pages are compressed." The default profile compresses only text/plain content; for HTML, CSS and JS, a profile with the content types added is required.
• "The Trusted Proxies default reads the X-Forwarded-For header." There is no default Trusted Proxies profile; if no profile is assigned, the client IP is not taken from the header.

How it is done in the documentation

• Timeouts · The Default Timeouts Profile Behavior
• vService Limits · The Default vService Limits Profile Behavior
• Compression · The Default Compression Profile Behavior
• Trusted Proxies · The Default Trusted Proxies Profile Behavior

Related questions

• Which profile types are there; which vService types can they be used with?
• How do I understand the impact of changing a profile before I change it ("Used in")?
• What is the vService Limits profile; what are the default limits?