Skip to content
Myra Online Help Updated · 21 Aug 2026

Expert tab

The Expert tab contains configuration options that define the settings in the Connection, Security, and Performance tabs more specifically.

The following settings are available:

Name Definition
Proxy Host Header Defines the custom proxy host header. The default value is the same as the subdomain.
Default value: $myra_host
Request limit block Defines how to respond to a request that exceeds the request limit.
The following options are available:
  • CAPTCHA: A CAPTCHA is shown to the user.
  • HTTP 429: The user receives a Too Many Requests message.
  • No: The user receives an HTTP 503 error code.
Default value: CAPTCHA
Request limit report Enables or disables logging when the configured request limit is exceeded.
Default value: Off
Contact email address(es) Defines one or more contact email addresses.NoteTo enter multiple contacts, they must be separated by spaces.Default value: NULL
Upstream connection header Defines the connection header transmitted to the customer infrastructure when a request is made.
The following values are available:
  • none: A header is not attached to the request. The default value connection keep-alive is used.
  • close: The connection close command is attached to the request.
  • upgrade: The client can send a clear-text request to the origin server that is later upgraded to a newer protocol version or replaced by another protocol. This is enabled by the connection upgrade command and is used for WebSocket.
Default value: none
Myra SSL/TLS Header Enables or disables the transmission of the X-Myra-SSL: true header for a request to your infrastructure. This setting helps identify whether the original request came via HTTPS, even if the value HTTP was set under Source protocol in the Connection tab.
Default value: Off
Cache bypass cookie name Defines the name for a cookie that forces Myra not to deliver the response from the cache.NoteIf you would like to use this function, the cookie value must not be null.Default value: NULL
Upstream connect timeout Defines the maximum time period in seconds for establishing a connection to your infrastructure.
Default value: 60s
Upstream read timeout Defines the maximum time period in seconds for reading the responses from your infrastructure.NoteThe value describes the maximum permitted time period between two consecutive read operations, not the time period for reading the entire response.Default value: 600s
Next upstream error handling Defines the errors that mark the current upstream as down.
The following options are available:
  • Use Default Value
  • Error
  • Timeout
  • Invalid Header
  • HTTP 500: HTTP 502
  • HTTP 504
  • HTTP 403
  • HTTP 404
  • Disable
Default value: Not available
Proxy cache stale handling Defines the errors in communication with the upstream server that a stale object from the cache should be used for.
The following options are available:
  • Use Default Value
  • Error
  • Timeout
  • Invalid Header
  • Updating
  • HTTP 500: HTTP 502
  • HTTP 504
  • HTTP 403
  • HTTP 404
  • Disable
Default value: Not available