Altova Mailing List Archives>Archive Index >microsoft.public.xsl Archive Home >Recent entries >Thread Prev - Re: IE Problem: XPath document() function and HTTPS >Thread Next - Re: IE Problem: XPath document() function and HTTPS Re: IE Problem: XPath document() function and HTTPSTo: NULL Date: 1/9/2007 11:56:00 AM "Steve" <Steve@d...> wrote in message news:9251A5A9-681F-4218-B683-0193CD641BA0@m...... > Anthony, you're my new hero :-) I eliminated all the HTTP headers I set > related to stopping browsers from caching my dynamically generated XML and > things worked in both IE 6 and IE 7 with HTTPS. Unfortunately, the XML got > cached (mmm, even with an HTTPS connection?) > and this therefore broke my > application. Yes WinInet does that. There is a switch somewhere that turns that off for secure content however I suspect using it will put you back to square one. When you say it got cached do you mean the a subsquent transform failed to request the content again? What ProgIDs are you using to instantiate the MSXML components? An MSXML3 DOM for example will by default include a pragma:no-cache in the request to load a DOM. This is what XSL uses internally to implement the xpath document() function. > So, as you originally suggested, I got rid of just no-store but > this caused things to revert back to the old problem. Hmm... WinInet will be using some logic (known only to itself) to determine whether or not to actually place the content in the cache. Normally with plenty of space available it would cache even things that are marked as no-cache. I suspect in the case where it is both no-cache and secure content it doesn't. Fundementally WinInet sometimes uses the cached copy of the file as a means of streaming it to the requesting client. If it can't create the file on disk it can't supply it. This problem most often occurs with secure or no-store PDFs. > So, it would seem that > setting the no-cache directive is also a problem here. I finally ended up > setting just the "Expires" header to zero and this didn't cause problems with > IE, plus it prevented the XML from being cached in both IE and Firefox (I > guess I was just being too fancy with all my "don't cache this" settings :-) It's odd as I've pointed out msxml by default will force a resync anyway despite the values in the cache-control or expires headers. > > I am happy with the world again. Thanks to you and thanks to Joe as well. > > Cheers, > -Steve > > "Anthony Jones" wrote: > | ||||||
| Company | Legal | Press | Partners | Careers | Sitemap | Contact Us | Altova Blog | Mobile | Full Site | |||
|
