J
jkostenbader
Without being able to provide you with a lick of code, I'd like to be
able to present you with a problem that I can get some general feedback
from:
A current Dephi application uses shdocvw.dll to wrap a nice browser
into its functionality. If an end user enters a website that requires
credentials of some sort generating a nonpersistant session cookie and
susequently clicks on a link that would normally spawn a new window
shdocvw.dll seems to treat that link as another instance of IE rather
than a child window. The result is that the end user is required to
re-enter their credentials. Hopefully this makes sense....if there are
questions I'm missing I'd like to have an ongoing dialog.
I guess the bottom line question is...its is possible to retain that
session cookie (thereby keeping the credentials) using shdocvw.dll
Regards
John
able to present you with a problem that I can get some general feedback
from:
A current Dephi application uses shdocvw.dll to wrap a nice browser
into its functionality. If an end user enters a website that requires
credentials of some sort generating a nonpersistant session cookie and
susequently clicks on a link that would normally spawn a new window
shdocvw.dll seems to treat that link as another instance of IE rather
than a child window. The result is that the end user is required to
re-enter their credentials. Hopefully this makes sense....if there are
questions I'm missing I'd like to have an ongoing dialog.
I guess the bottom line question is...its is possible to retain that
session cookie (thereby keeping the credentials) using shdocvw.dll
Regards
John