I ran in to this same problem. The issue is that since everything in https
is supposed to expire immediately (meaning not be cached because it is
secure), IE actually expires the XML that's returned after it gets to the
page object but before making it available to any content on the page, such
as
All,
I have a really odd problem that has manifested itself now that we have moved a
data-driven site with a Flash front end to https. The front end is at
https://www.vte.cert.org/vte1_5/vtelibrary.html. When you click the 'go' button
in the Flash app, it triggers an XMLConnector component that
2 matches
Mail list logo