Try hitting the servlet container (tomcat/jetty) direct instead of going through the apache proxy. Do you still see the issue?
If the issue doesn't occur when hitting direct, you've isolated the problem as an apache proxying issue. It's now time to start inspecting the HTTP traffic in both cases. Keep an eye out for request / response headers that are not being proxied through apache. It sounds like this issue might be off topic for this list and a more general apache config issue. -- View this message in context: http://tapestry.1045711.n5.nabble.com/Base-page-action-with-null-session-object-tp5716584p5716589.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
