Avoiding duplicates
When capturing both sides of the same communication - for instance, when capturing from both the gateway and the service itself - Spider captures twice the same communication, with sightly different dates.
It is now possible to ask Spider to avoid duplicates.
Avoiding duplicated communications​
With this option, Spider will generate the same id for the object on both side of the communication, and only one will be then saved (and parsed).
For this, select 'Avoid duplicated communications' on Capture Config tab.
Then, only one Tcp session will be created, and thus, only one example of the Http Communications.
Avoiding duplicated packets​
You may also chose to avoid duplicated packets, on the advanced options of the Packets saving part of Parsing Config tab. The options is visible only when saving packets.
Note that this is asking more resources in of the system, and should be only considered when doing statistics at the packet level (not often).