You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jetspeed-user@portals.apache.org by Paul Spencer <pa...@mikon.com> on 2001/10/07 16:13:46 UTC
Re: Local WebPagePortlets ignore cache-control and expire in HTTP header
This problem has been fixed as of 07-oct-2001 9:00 AM EST. The
WebPagePortlet will cache it's content based on the expires field in the
HTTP Response header. It will NOT honor the expiration time set in the
<META > tag.
Paul Spencer
Paul Spencer wrote:
>
> The value of Cache-Control and Expires in the HTTP header are ignored
> for web pages that are considered local. This problem occurs for
> WebPagePortlet and HTML portlet types.
>
> The following JSP should not be cached, but it is by the WebPagePortlet
> when the Jetspeed considers the page local. By contrast the portlet
> JavaWeb is never cached and it is remote with an expiration date set in
> the HTTP header.
>
>
> <%@ page language="java"
> import="java.util.Date" %>
>
> <%
> response.setHeader("Pragma", "no-cache");
> response.setHeader("Cache-Control", "no-cache");
> response.setDateHeader("Expires", 0);
> %>
> <html>
> <head>
> <title>Time on the server</title>
> </head>
> <body>
> <strong>The current time is <%= new Date() %></strong>
> </body>
> </html>
>
> I have looked in the code, but I have not found where the Local cache
> entries are created and expired. Ideas?
>
> Paul Spencer
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
> For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: jetspeed-user-unsubscribe@jakarta.apache.org
For additional commands, e-mail: jetspeed-user-help@jakarta.apache.org