Guest


9/13/2018
Guest
I’m trying to debug a flow that interacts with a web service using Fiddler, but I’m running into an issue: As described in this article http://docs.telerik.com/fiddler/observe-traffic/troubleshooting/notraffictolocalhost Fiddler cannot capture traffic from Localhost or 127.0.0.1 being hit, but instead must capture local traffic using the machine name. I was noting that I can’t login to decisions from any outside machine, and am now noticing that when I hit the machine name locally the same behavior occurs. The login screen is visible, but it repeatedly tells me my password is wrong despite it being correct. Any suggestions?
0 mark as "accepted answer" link reply with quote
althea@decisions.com
althea@decisions.com
Administrator
Posts: 106


9/13/2018
althea@decisions.com
althea@decisions.com
Administrator
Posts: 106
Fiddler needs to be added as a proxy in DecisionsServiceHost.exe.config (which can be found in C:\Program Files\Decisions\Decisions Services Manager). This can be done by adding the following block and then restarting Service Host Manager:



This article from Telerik may be helpful: http://www.telerik.com/blogs/capturing-traffic-from-.net-services-with-fiddler
edited by Althea on 9/13/2018

0 mark as "accepted answer" link reply with quote
brandon.roberts@decisions.com
brandon.roberts@decisions.com
Administrator
Posts: 35


16 days ago
brandon.roberts@decisions.com
brandon.roberts@decisions.com
Administrator
Posts: 35
As a Note here you will need to add this Fiddler Block within the AssemblyBinding block of the DecisionsServiceHost.exe.config File
0 mark as "accepted answer" link reply with quote


(Ctrl+Enter)




Powered by Jitbit Forum 8.3.8.0 © 2006-2013 Jitbit Software