Shall I be honest? :)
Fiddler logs are a complete waste of everyone's time. They tell you what
was sent to/from the browser, but the issue is client side - it's the
browser executing the Javascript code.
Theoretically, one could use some home-brew tool to pump Fiddler logs to
a browser and try to debug it, but that's going to be so painful (not
least because you don't have the customer's browser) that the only way
to actively tackle it is to use a Javascript debugger on the client site.
Failing a webex: The ClientCore.js files shipped with BMC are
"compressed", which is basically an ineffective way to make them
unreadable to the client - there are dozens of tools to format them
neatly. I would expect someone to send you an uncompressed ClientCore.js
file and ask for a screenshot of the error from the Error console in
Firefox, which allows you to at least pinpoint the problem. Even better,
IE's debugger used to have a "break on exception and display the stack"
feature, but I've not used that in years. This information will provide
clues.
Fiddler logs are for solving client/server side issues, such as "Why is
my browser failing to authenticate single-sign on with this service?".
Pascale: If SSL options are being suggested, I'm not sure anyone
understands the problem...
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
