My guess is that the HTTP/1.1 headers that JRun sets by default
(Cache-control: no-cache=set-cookie,setcookie2 ???) take precedence over
the HTTP/1.0 header that you are setting. Verify what headers are
actually getting set through telnet.
I believe JRun is setting headers like this so that the session cookie
never gets cached, and coders can program shortcut responses if an
If-modified header is set. It would be great if someone could confirm this.
[EMAIL PROTECTED] wrote:
> Hi,
>
> I have a caching problem with JRun. If I use the HTML <META HTTP-EQUIV> tag
> to specify no caching,
> it works fine. But when I use the setHeader() method to specify the same, it
> doesn't work. I would
> like to know why this is happening.
>
> res.setHeader("Pragma","no-cache") ; // DOESN'T WORK, calling
> this before calling getWriter()
> out.println("<META HTTP-EQUIV='Pragma' CONTENT='no-cache'>") ;
> // WORKS
>
> I tested with the following:
>
> Servers: JRun 3.0 on both Windows NT & HP-UX 11.00
> Clients: IE 4.0, Netscape 4.06
>
> Thanks,
> Suresh
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Your ad could be here. Monies from ads go to support these lists and provide more
resources for the community. http://www.fusionauthority.com/ads.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists