The users cannot download or upload large files from the OAG-managed application. 

• Okta Access Gateway (OAG)
• Large file download or upload
• High network latency
• Slow end-user machine

Due to a network-related issue between the OAG server and the client, the OAG appliance is not able to offload the data fast enough, and the NGINX service can close the connection prematurely. The users are not able to download or upload large files from the OAG-managed applications. The download or upload terminates after some time without any errors in the logs. 

By default, the settings are set to what is shown below (value in seconds):

client_body_timeout 10;
send_timeout 5;

The following directives can help when set under the advanced policies in the OAG app configuration:

• Directive send_timeout sets a timeout for transmitting a response to the client. The timeout is set only between two successive write operations, not for the transmission of the whole response. If the client does not receive anything within this time, the connection is closed. 
  • The example below shows the value set to 5 minutes, and it is important to understand that this will need to be modified to meet specific needs.

    send_timeout 5m;

• If the above directive does not help, then client_body_timeout needs to be added as well. This defines a timeout for reading the client request body. The timeout is set only for a period between two successive read operations, not for the transmission of the whole request body. If a client does not transmit anything within this time, the request is terminated with the 408 (Request Time-out) error.
  • The example below shows the value set to 5 minutes. It is important to understand that this will need to be modified to meet specific needs:

    client_body_timeout 5m;