---
title: Trace HTTP/S communications issued by Sitecore
slug: '2529'
canonical_url: https://docs.coveo.com/en/2529/
collection: coveo-for-sitecore-v5
source_format: adoc
---
# Trace HTTP/S communications issued by Sitecore
:experimental:
Sometimes, it's very handy to monitor the outgoing traffic from a Sitecore instance to various other services, such as [Coveo Platform](https://docs.coveo.com/en/186/) services.

This article explains how to use [Fiddler](https://www.telerik.com/fiddler) for this purpose.

## Step 1: Configure Fiddler as the proxy

. Enable HTTPS decryption.
 .. In Fiddler menu, select **Tools > Options**.
 .. Select the **HTTPS** tab.
 .. Check the **Capture HTTPS CONNECTs** checkbox.
 .. Check the **Decrypt HTTPS traffic** checkbox.

![Screenshot of Fiddler interface showing the Decrypt HTTPS traffic checkbox](https://docs.coveo.com/en/assets/images/c4sc-v5/37099718.png)

 .. When prompted, authorize the Fiddler certificate.
 .. Close the dialog.
. (Optional) You can enable filters to only monitor calls made to specific hosts.
 .. Click the **Filters** tab on the right side of the screen.
 .. Check the **Use Filters** checkbox.
 .. In the **Hosts** section.

![Screenshot of Fiddler host filtering interface](https://docs.coveo.com/en/assets/images/c4sc-v5/37099719.png)

  ... Set the first dropdown menu to **No Zone Filter**.
  ... Set the second dropdown menu to **Show only the following Hosts**.
  ... In the text area, enter the following host names.

For example, to monitor calls made to Coveo, use these host names:

   **** `platform.cloud.coveo.com`
   **** `api.cloud.coveo.com/push`
   **** `s3.amazonaws.com`

  ... Click the **Changes not yet saved** label to apply the changes.

![Screenshot of Fiddler interface with the Changes not yet saved label | Coveo](https://docs.coveo.com/en/assets/images/c4sc-v5/37099720.png)

## Step 2: Configure Sitecore to use the proxy

> **Note**
>
> Fiddler must be running.
> Otherwise, the Sitecore instance won't be able to perform any outgoing request.

. Edit the Sitecore `web.config` file.
. Add the following XML snippet as an immediate child of the `<configuration>` element.

```xml
 <system.net>
   <defaultProxy enabled = "true" useDefaultCredentials = "true">
     <proxy autoDetect="false" bypassonlocal="false" proxyaddress="http://127.0.0.1:8888" usesystemdefault="false" />
   </defaultProxy>
 </system.net>
```

. Save the `web.config` file.
. Recycle the Application Pool.

## Step 3: Capturing the traffic

. Ensure that Fiddler is capturing traffic.
Look at the capture indicator at the bottom left corner of the window.
Use the F12 key to toggle capture.

![Screenshot of Fiddler interface showing the Capturing status | Coveo](https://docs.coveo.com/en/assets/images/c4sc-v5/37099721.png)

. In Sitecore, perform the action you want to monitor.
. As the task progresses, you should see the network traces appear in Fiddler.
. Once the task completes, save all the Fiddler sessions as a **.saz** file.

> **Important**
>
> Make sure to revert the proxy setting in the Sitecore configuration before you close Fiddler.