> ProxyPass / http://internal.server.name/
> ProxyPassReverse / http://internal.server.name/
>
> When coming into the application from the Internet the homepage loads,
> one can get to the application, authenticate and retrieve a page based
> on query data entered into the application page.
> Then the problem arises: the page returned by the query contains links
> to drill down further to specific information. When a user clicks on
> one of the links the application blows up, returning a huge websphere
> error message, notably:
> WF0119: Error occurred while refreshing the screen
> and
> WF0025: In ControllerRequestHandler.displayScreen(), an exception
> occurred while forwarding to /styles/chrome/PageBuilder.jsp
>
> Again, this hasn't happened when running without the (Reverse)Proxy.

sounds like you're in for some time with a packet sniffer. first do
the action blowing up over the proxy connected directly to the server
and sniff with ethereal on the client. use "follow tcp stream" to see
what is going on. keep a copy of the cleartext. then do the same over
the reverse proxy and keep a copy. then run a sniffer on the reverse
proxy on the backend interface to see what is going to the backend (if
you can't have ethereal on the proxy use tcpdump -i <backend-if> -s
1500 -w dump, copy over dump and read it into etheral for analysis.
then compare all three - look for differences. maybe there's headers
added or missing or data truncated, maybe it's just the fact that
mod_proxy uses no keepalive to the backend.

joachim, who has to do things like thas´t more often than he likes...