Tracing HTTP(S) Communications Issued by Sitecore
Sometimes, it is very handy to monitor the outgoing traffic from a Sitecore instance to various other services, such as Coveo Cloud.
This article explains how to use Fiddler for this purpose.
Step 1 - Configure Fiddler as the Proxy
- Enable HTTPS decryption.
- In Fiddler menu, select Tools > Fiddler Options.
- Select the HTTPS tab.
- Check the Capture HTTPS CONNECTs checkbox.
Check the Decrypt HTTPS traffic checkbox.
- 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-hand part of the screen.
- Check the Use Filters checkbox.
In the Hosts section.
- Set the first drop-down to No Zone Filter.
- Set the second drop-down to Show only the following Hosts.
In the text area, enter the following host names. For example, to monitor calls made to Coveo Cloud, use these host names:
Click the Changes not yet saved label to apply the changes.
Step 2 - Configure Sitecore to Use the Proxy
Fiddler must be running. Otherwise, the Sitecore instance will not be able to perform any outgoing request.
- Edit the Sitecore
Add the following XML snippet as a peer to the existing
<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
- Recycle the Application Pool.
Step 3 - Capturing the Traffic
Ensure that Fiddler is capturing traffic. Look at the capture indicator in the bottom left corner of the window. Use the F12 key to toggle capture.
- 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.
Make sure to revert the proxy setting in the Sitecore configuration before you close Fiddler.