I'm not 100% sure that tapestry has set the header since response.containsHeader() returns false. It's probably best to debug to be sure.
My gut feeling is that gae is having troubles with setting a header after writing to the response body. Although tapestry is doing this legally, under normal circumstances this is not allowed. Normally response headers must be written before the body. Perhaps the new version of gae is making this assumption in its implementation -- View this message in context: http://tapestry.1045711.n5.nabble.com/Tapestry-Problem-on-Google-App-Engine-in-Development-tp5716763p5717186.html Sent from the Tapestry - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
