---
title: "Optional: Configuring ASE persistent connections"
description: You can optionally configure TCP keep-alive connections in the ase.conf file of API Security Enforcer (ASE).
component: pingintelligence
version: 5.2
page_id: pingintelligence:pingintelligence_integrations:pingintelligence_configure_persistent_connections_axway
canonical_url: https://docs.pingidentity.com/pingintelligence/5.2/pingintelligence_integrations/pingintelligence_configure_persistent_connections_axway.html
revdate: April 3, 2024
section_ids:
  about-this-task: About this task
  steps: Steps
---

# Optional: Configuring ASE persistent connections

You can optionally configure TCP keep-alive connections in the `ase.conf` file of API Security Enforcer (ASE).

## About this task

The following is a snippet of `ase.conf` displaying the default `enable_sideband_keepalive` variable. The default value is set to `false`.

```
; enable connection keepalive for requests from gateway to ase.
; This setting is applicable only in sideband mode.
; Once enabled ase will add 'Connection: keep-alive' header in response
; Once disabled ase will add 'Connection: close' header in response
enable_sideband_keepalive=false
```

If this variable is set to `true`, then you must configure persistent connections in Axway Policy Studio:

## Steps

1. In Axway Policy Studio, go to **Environment Configuration → Listeners → API Gateway**.

2. Click your ASE IP address in **Sample Services**.

3. In the **Remote Host Settings** pop-up window, clear the **Allow HTTP 1.1**check box.

4. Click the **Include Content Length in request** check box. Make sure all other check boxes are cleared.

5. Click **OK** and deploy the policy.

   ![A screenshot of the Remote Host Settings window with Include Content Length in request highlighted with a check box.](../_images/qjb1564009212694.png)