Doug, I appreciate the suggestion about replacing the appshell code in nsPSMUICallbacks.cpp with a callback into my custom app which would open a new window, however, because my app has no ui, I would rather see either of your prior suggestions implemented. See your response to 1/10/2001 post for "Just a little fyi" netscape.public.mozilla.netlib ........ "What I think we need is (a) a way to have PSM not display these dialogs. Instead the client should receive some kind of callback so that it can determine if the user should see a dialog. Maybe this is what the psm UI handler turns into? (b) We need to be able to pass client context per request which will be passed back to us in these callback. Right now, you only have one client context for every connection. There will be no way to pass the requesting window around so that we can display module dialogs without this prerequest client context. I think that both of these are in the works. Javi or David could comment on the timeframe they are currently looking at." ----- Original Message ----- From: Doug Turner To: Gagan Saksena Cc: Rick Marvin ; Darin Fisher ; [EMAIL PROTECTED] Sent: Monday, January 15, 2001 1:39 AM Subject: Re: trouble with https request within custom necko app I can explain this: PSM does not have a very good embedding story. Basically, PSM requires that a "hidden window" to be around so that when psm needs to display a dialog, the client has some parent window to modal it against. The current design of PSM does not allow per request context to be passed around. If the designed offered this, I could have passed the parent window into these callsback instead of relying on this hidden window. If you take a look right here, you will see the code that gets executed when an error or warning needs to be displayed to the user. http://lxr.mozilla.org/seamonkey/source/extensions/psm-glue/src/nsPSMUICallb acks.cpp#92 The url that you are seeing in your logs suggest that the site that you are going to has a bad cert - for whatever reason. Please note that 4.x or IE may not display the same warnings. Jud, I believe that you will have to see about this getting fixed as well. We could hack some kind of solution so that we open new windows that are not bound to any parent if no parent exists. We could also just ping Bob Lord's team regarding a real fix for this. Rick, could you try replacing the appshell code in nsPSMUICallbacks.cpp, with a callback into your custom app which would open a new window? Gagan Saksena wrote: Rick: I am cc'ing dougt who might be able to comment more on this. Since this is your custom app, I am not sure what could be going wrong, but I would start with making sure that you are initializing all the relevant things for PSM and that PSM is running successfully on your local machine. -Gagan Rick Marvin wrote: I'm still having trouble with https request within my custom necko app. I have come across something while compairing the log files that are generated when mozilla makes the https request with the log files generated when my custom app makes the https request. Both files start out the same, however, after we leave the nsSocketTransport::Process method, my custom app hangs, while mozilla goes and generates a new nsHTTPChannel for URI: http://3:[EMAIL PROTECTED]:2112/get?baseRef=bad_server_cert _unknown_issuer1&target=4. This happens to be the same URL that the psm server log references in its log file. Can you explain what this is? Is this somehow connected with the load group for the channel? -- Doug Turner [EMAIL PROTECTED]
