Bertrand Delacretaz wrote: > > I see your point - in the meantime I've worked around the problem by > storing cache-related info in a Request attribute and generating the > headers later in a non-internal part of pipeline. > > I also found out that (in the 2.1.7 release at least), pipelines called > via map:mount also eat HTTP response headers set in code , *including* > content-length which might have been set by the mounted pipeline. > > There's a related discussion at > http://marc.theaimsgroup.com/?t=111746450000002&r=1&w=2, I think this > deserves further investigation, in my view map:mount should completely > delegate to the mounted sitemap, without filtering. > What does this currently mean? If I set headers in a sub sitemap they are ignored?
Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/
