In some cases you may need to see what a site is sending out for Find requests. See below on how to setup Fiddler for that.
- In order for Fiddler to catch requests from Find, it needs to be a proxy or the man in the middle of the requests. Add a proxy to the web.config below the <system.net> tag.
<!-- The following section is to force use of Fiddler for all applications, including those running in service accounts -->
<defaultProxy enabled = "true" useDefaultCredentials = "true">
<proxy autoDetect="false" bypassonlocal="false" proxyaddress="http://127.0.0.1:8888" usesystemdefault="false" />
<servicePointManager checkCertificateName="false" checkCertificateRevocationList="false" />
- After making the change, install and run Fiddler.
- Ensure that decrypt https is turned on in Fiddler (Tools > Options > HTTPS).
- Begin capturing(F12) if it is not already on.
- Turn off filters. They often restrict traffic to only the URL of used by IIS Express, which prevents viewing of data sent to Find.
- Attempt a search on the site. You should see Find requests going to the service URL(located in the web.config). The following shows the _search requests and you also see that filters are off.
Note: If you do not see requests to the find endpoint, see step 3 and clear application cache via a restart or other method(caching can prevent new requests). In the above screenshot you can see requests to the host es-eu-dev-api01.episerver.net. Check the serviceURL value in the web.config to identify the find endpoint.
- Once done, turn off capturing in the file menu or F12.
- If you need to specifically capture bulk requests, filter on @fields.action.keyword or @fields.action = bulk. Make sure the URL is not restricted on the site's hostname or you will miss Find traffic.
- If you are verifying that Find caching works, make sure that identical searches(e.g. searching for example twice or more) only outputs one request to the Find service URL. You can also use Fiddler to verify how long requests are being cached.