Has anyone else had this problem? I was using AutoResponder to test without having to reload on my test box every time I made a change - it was working. I was redirecting from the web server on my VM to a share on my development machine (Y:\Dev\somescript.js). Then, suddenly, with no changes to either machine other than the obvious code changes to somescript.js, I was getting 404 errors on the file. If I change the redirect to a local drive (C:\Dev\somescript.js), the AutoResponder works fine - but this is really not an option for me, for several reasons. I can open the file through the File Explorer on the VM, so the mapping is still there.
This happened to me before and after multiple hours of troubleshooting, I simply re-installed Fiddler and it started working again - for a while; now, re-installation doesn't even fix it.
Obviously, I can work around it, by just re-deploying to my VM *every* time I make a change, but that adds a lot of steps and opportunity for error that I was able to work around when AutoResponder was working for me.
Further Info: VM is Windows 2008 R2, Hardware Dev is Windows 7, running Internet Explorer 9, have even tried several of the spiffy tricks, like the localhost "dot trick", using ipv4.fiddler, etc (that I shouldn't need since I'm not on IE8, but desperate times and all that....)
Any help or suggestions would be greatly appreciated.
This happened to me before and after multiple hours of troubleshooting, I simply re-installed Fiddler and it started working again - for a while; now, re-installation doesn't even fix it.
Obviously, I can work around it, by just re-deploying to my VM *every* time I make a change, but that adds a lot of steps and opportunity for error that I was able to work around when AutoResponder was working for me.
Further Info: VM is Windows 2008 R2, Hardware Dev is Windows 7, running Internet Explorer 9, have even tried several of the spiffy tricks, like the localhost "dot trick", using ipv4.fiddler, etc (that I shouldn't need since I'm not on IE8, but desperate times and all that....)
Any help or suggestions would be greatly appreciated.
1 Answer, 1 is accepted
0
Hello, Jesse--
Reinstalling Fiddler isn't going to fix anything.
The body of the 404 message, as shown in Fiddler, contains some content. What is that content? Use the RAW response viewer to get it.
Regards,
Eric Lawrence
Telerik
Reinstalling Fiddler isn't going to fix anything.
The body of the 404 message, as shown in Fiddler, contains some content. What is that content? Use the RAW response viewer to get it.
Regards,
Eric Lawrence
Telerik
Check out the Telerik Platform - the only platform that combines a rich set of UI tools with powerful cloud services to develop web, hybrid and native mobile apps.