As the title suggests, any thoughts appreciated to run this down, something is right in front of me that I can no longer see, so appreciate any pointers,
I'm replacing a requested .js file with a local file using Autoresponder.
But, javascript errors started showing up (console error messages under devtools) when the Autoresponder rule was active and replacing the request with a local .js file, and disappeared when turned off and the original file served.
In order to work out what was going on, I grabbed the contents of the original file, saved it locally, and used that to replace the .js requested by the page. But, still getting the same .js errors showing!
Verified the local file was exactly the same contents as the served file, and the Autoresponder rule works, so, what is happening that causes the use of Autoresponder to cause replaced javascript to throw errors?
??? What the...... ?
I've worked Autoresponder too many times to count, it works great,
And, this is just javascript, copied directly from the response from the server, which works perfectly fine (no console errors) when Autoresponder is turned off, but, when Autoresponder is turned on and replacing the requested .js file with a local copy of the same file, devtools console reports all kinds of errors (missing references, etc...,
eg.,
account.js:2
Uncaught ReferenceError: fb is not defined
at success (account.js:2)
at Object.cb [as success] (logout.jsp?DPSLogout=true:389)
at o (jquery.min.js:2)
at Object.fireWith [as resolveWith] (jquery.min.js:2)
at w (jquery.min.js:4)
at XMLHttpRequest.d (jquery.min.js:4)
Thanks for your help,
KWL
starting Fiddler stops a running docker process.
stopping Fiddler shuts docker demon down completely.
docker version: 17.09.0-ce
Mono version: 5.4.201
Fiddler version: Beta downloaded 31-Oct-2017
Macos version: Sierra 10.12.6
Workaround: start docker process after starting Fiddler
Let me know if there's anything I can do to support investigation.
I used to change Fiddler script to add the automatic authentication to make console based applications work with NTLM authentication, however my company has moved from TMG to McAfee Web Gateway and now the code below is not working.
oSession["X-AutoAuth"] = "domain\user:mypass";
CONNECT www.telerik.com:443 HTTP/1.1
Host: www.telerik.com:443
User-Agent: Fiddler/4.6.2.32002 (.NET 4.6.2; WinNT 10.0.14393.0; en-US; 4xAMD64; Auto Update; Full Instance)
Proxy-Authorization: Negotiate TlRMTVNTUAABAAAAl4II4gAAAAAAAAAAAAAAAAAAAAAKADk4AAAADw==
HTTP/1.1 407 authenticationrequired
Via: 1.1 172.99.71.201 (McAfee Web Gateway 7.6.1.1.0.21006)
Date: Fri, 30 Sep 2016 18:11:09 GMT
Content-Type: text/html
Cache-Control: no-cache
Content-Length: 3007
Proxy-Connection: Keep-Alive
Proxy-Authenticate: NTLM
Proxy-Support: Session-Based-Authentication
Can you help me?
Hi - I have an application (.exe) that was written in Python. It makes a HTTPS call out and data is returned in JSON. With Fiddler running, I can run the program, it makes 2 web calls and bring back data.
As soon as I enable Fiddler for HTTPS and Decryption, the program won't return data.
I enabled the CERT from Fiddler and made sure the proxy was correct in my LAN settings. Any ideas? (Windows 10)