Have you tried loosening up the refresh to let's say 5 seconds? Sounds
to me like the refresh rate is too intense for a proxy environment.
Another way to go (and I don't have the sample code) is to use a little
javascript and some AJAX techniques for updating the page without a
round trip.
--David
Kristian Rink wrote:
Hi David, @list;
first off, both thanks a lot for pointing me the right way, and let me
apologize, as well, as this seems to be a question where RTFM would have
been helpful before bothering the list - however, I wasn't aware that
tomcat would need a special setup in order to run behind a proxy.
By now, it basically is working the way I want it, leaving only one
issue: This whole configuration is just almost unusable in our
environment.:/ One of the core parts of the application to be proxied
relies upon refreshing frequently (read, each second) using "Refresh"
headers, and somehow this doesn't seem to work accessing the page from
the outside through the apache2 proxy. There are several different
phenomenons to appear almost randomly:
- Sometimes, the "Refresh" of the site works well, the result is
displayed well.
- Sometimes, the site refresh ends up displaying a "302 moved - this
document is <a..>here</a>". This sometimes also includes partial or full
textual output of the page to be refreshed.
- Sometimes, just nothing happens, ending with a blank page.
Depending on how the proxy is configured (using mod_proxy or
mod_rewrite), things are better or worse but never really pleasing.
Questions, this way:
- Can I get "Refresh" headers through a reverse proxy in a working way
with a configuration like that?
- Is this strange behaviour more likely to be a matter of configuration
or of slow network / hardware?
- Right now I am looking at mod_jk(2) to see how this will do - is this
likely to get me out of this trouble given that tomcat and apache2 are
running on different hosts?
Thanks a lot for any inspirations and help.
Bye,
Kristian
David Smith schrieb:
The connector receiving request from Apache needs at least the first
attribute added to it:
proxyName="domain.name.com": the domain name of the Apache httpd server
acting as a front end to Tomcat
proxyPort="80": the port number of the Apache httpd server
There is a sample of this in the server.xml distributed with tomcat.
---------------------------------------------------------------------
To start a new topic, e-mail: users@tomcat.apache.org
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]