You can customize the behavior of the
curl command by creating a file at
/home/cloudshark/.curlrc that contains some of the following command-line
options. The file MUST be readable by the
cloudshark Linux user. If it does
not exist, it will be created by the installer. It’s OK for this file to be empty
if you do not wish to tweak any settings.
There are a multitude of additional options that you can configure within curl
to control how captures are fetched. The full documentation for the
command is available at https://curl.haxx.se/docs/manpage.html.
By default, CloudShark will limit the allowed protocols for fetched URLs to be
https only. Additionally,
file can be enabled from the CloudShark
GUI. If you would like any additional protocols enabled, they can be specified in the config file.
If you are fetching from web servers using self-signed certificates, you may wish to enable ‘insecure’ mode which will not verify the certificate. The transmission will still take place over SSL.
CloudShark will not follow URL redirects by default when fetching a capture file. This is considered insecure over HTTP and capture security is important to us. If it is necessary for you to follow redirects when importing by URL, you will need to add this option.
CloudShark requires that the entire curl command take no longer than 55 seconds. This is to avoid a timeout with the web browser. This timeout can not be extended longer than that. However, if you would like to shorten that timeout for performance reasons, there are two options to consider.
The total time allowed for the entire transmission:
The time allowed for the TCP connection to take place:
If your CloudShark server needs to access a Proxy server in order to fetch URLs, proxy support should be added here too.