There's a bug which leads to trace records of resources being filtered even if the Filter resources button is deactivated.
This happens because the CSS class displayAnyway isn't appended to a resource-request in the attachResponseToRequest function. Only a click on Filter resources adds the class to the resource-requests.
The correct behavior would be to add the class directly within attachResponseToRequest function if the current state of filterResources is false.
Current behavior in SAML-tracer v1.5.1
Notice the filtered requests even though the filter button is not active:
This pull request corrects the behavior as shown beneath
There's a bug which leads to trace records of resources being filtered even if the Filter resources button is deactivated.
This happens because the CSS class
displayAnyway
isn't appended to a resource-request in theattachResponseToRequest
function. Only a click on Filter resources adds the class to the resource-requests.The correct behavior would be to add the class directly within
attachResponseToRequest
function if the current state offilterResources
is false.Current behavior in SAML-tracer v1.5.1 Notice the filtered requests even though the filter button is not active:
This pull request corrects the behavior as shown beneath