Well, the code snippet I linked to below is from my actual border
component, and here's what the output looks like:!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd";> <!-- Application: Corinna --> <!-- Page: LoginSuccess --> <!-- Generated: Mon Aug 15 08:08:11 PDT 2005 --> <html> <head> <meta name="generator" content="Tapestry Application Framework, version 3.0.3"/> <meta http-equiv="Content-Type" content="text/html;charset=UTF-8"/> <title>Demo Application</title> <link rel="stylesheet" type="text/css" href="/Corinna/css/corinna.css"/> </head></html> <!-- Render time: ~ 0 ms --> <html> <META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE"> <META HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE"> <head> </head> So it sure looks like it's working unless my limited html skills have escaped me and your browser ignores the second set of meta tags? On FireFox (1.0.6), it's definitely parsing the NO-CACHE meta tags because they show up in the pageinfo dialog (I'd include a ss but I don't want to spam the list). --- Pat > -----Original Message----- > From: Kevin Menard [mailto:[EMAIL PROTECTED] > Sent: Monday, August 15, 2005 8:08 AM > To: Tapestry users > Cc: [EMAIL PROTECTED] > Subject: Re: set http headers (cache-control, etc) in tapestry > > Hi Patrick, > > On Aug 15, 2005, at 10:54 AM, Patrick Casey wrote: > > > > > I think you can just put them in your .html files and/or your > > border > > component (if you have one, can't you) e.g. > > > > > > <span jwcid="$content$"> > > <span jwcid="@Shell" stylesheet="ognl:assets.stylesheet" title="Demo > > Application" /> > > > > <html> > > <META HTTP-EQUIV="CACHE-CONTROL" CONTENT="NO-CACHE"> > > <META HTTP-EQUIV="PRAGMA" CONTENT="NO-CACHE"> > > </html> > > </span> > > You mentioned this once before, but I'm pretty sure this is going to > render invalid HTML. The Shell component should write out its own > head block. Feel free to correct me if I'm wrong though. > > For such things, I provide a bean to the delegate parameter of the > Shell component and all is good. Not the simplest solution I could > think of, but it does work. > > -- > Kevin --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
