User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:126.96.36.199) Gecko/2009042316 Firefox/3.0.10 (.NET CLR 3.5.30729) Build Identifier: 0.9.87.4 The debugger stopped working after we started using nCipher card (hardware SSL certificate) that replaced software certificate. Unable to troubleshoot any web apps issues without this tool , it was a lifesaver until it stopped working .Any help is appreciated. Reproducible: Always Steps to Reproduce: 1.try to access a web page from https: URL using hardware certificate 2.place breakpoint right at the beginning and access the URL from the browser 3.It hangs Actual Results: 1.try to access a web page from https: URL using hardware certificate 2.place breakpoint right at the beginning and access the URL from the browser 3.It hangs Expected Results: It hangs .. debugger does not do anything and i have to close the entire debugger and browser session. should have assisted me with debugging the web pages line by line as it used to before using software certificate
Why is anybody not workign on it.. it worked before using software certs and now it is not. CAN ANYONE LOOK INTO IT PLEASE.
(In reply to comment #1) > Why is anybody not workign on it.. it worked before using software certs and > now it is not. CAN ANYONE LOOK INTO IT PLEASE. Few people are working on Venkman at the moment, so it is hard to get stuff done, and there is a lot of stuff. When you say "software certs", you do mean client-side certs as well, right? My best guess at this point is that, in order to get the source, Venkman will re-request the page. In order to do that, it will re-use the security info for your original request (or so I'd hope, and suspect if it worked with software certs). I guess it might not work because the hardware (or software talking to the hardware) doesn't deal well with multiple requests to the hardware device... Have you tried enabling pretty print (button with the flower) - does that help?
Shasi, could you advise if my comment helped solve the problem, and/or answer my other questions? That way I can close the bug if it is no longer an issue, or continue working with you to see what the problem is and what could be done to fix it...
I am sorry , I just saw your comment today. I will try that option and let you know early next week. previously the URL used to access the web application was https:/... hosted on IHS server. A server certificate was issued for this URL. I was able to access the app turn on debugger and see it as i step thru the application. Now after we started using hardware certs (still server certs) the URL is the same , it hangs at the login page. I even tried login into application first and then turn on debugger , open the web URL directly in debugger and place breakpoint and when i refresh the application it is not stopping anymore, it hangs. It basically stopped working. I will try your option of using pretty print and see what happens.
I tried pretty print , it is not working. It just basically stopped when i started using hardware cert for my URL hosted on IHS server. All my steps that i used to follow to set breakpoint and then run click on pages to reach that breakpoint and then step thru the code from there .. all stopped working. Any help is much appreciated.
(In reply to comment #5) > I tried pretty print , it is not working. It just basically stopped when i > started using hardware cert for my URL hosted on IHS server. All my steps that > i used to follow to set breakpoint and then run click on pages to reach that > breakpoint and then step thru the code from there .. all stopped working. Any > help is much appreciated. Hmm. I don't actually know anything about hardware certificates. I'm not sure why pretty print would not work - it should work by decompiling the loaded script, which should be possible if the script is also running. When you say Firefox hangs, do you mean it becomes entirely unresponsive?
Yes. If I place a breakpoint in a .htm or .js script file. It used to stop before now it does not stop at the breakpoint anymore as if the I am viewing the webpage without the debugger turned on.