(sorry about the cross-post andycat, this is kinda urgent) So the stuff written below is only part of the solution. Turns out that if the web-client making the request is in /etc/hosts, the response is quick. If not, the response is painfully slow. Which seems like a host resolution issue somewhere. I can't find anywhere in the apache conf that tells it to resolve hosts (forward or backward), but in the access.log, the hosts appear a names (i.e. references to my laptop appear as think.local). If I add think.local to /etc/hosts it speeeds up. If I try to resolve using the locally running DNS server, think.local or the laptop's IP address, I either get a 'domain not found' or 'could not contact DNS server' after 10 or so seconds (similar delay to the web page loading).
Ideas? On Wed, Jul 1, 2009 at 10:12 PM, victor rajewski<[email protected]> wrote: > FYI: > > I encountered a problem today where plone would respond very quickly > when accessed directly through port 8080, but as soon as I accessed it > through an apache rewrite statement it became extremely sluggish > (>10second load time), even on the localhost. There were no errors, > the rewriting was happening correctly, I really couldn't work out why > there was a problem. Eventually I tracked it down to be a name > resolution error. Two things that can be used to solve this problem: > adding ServerName to the apache config outside any Virtualhosts. This > is a good idea to do anyway, but is often forgotten. The other thing > which works (independently of the ServerName fix) is to add all > possible machine aliases to /etc/hosts, all pointing to something in > 127.0.x.x. > > vik > _______________________________________________ Discuss mailing list [email protected] http://lists.plumi.org/listinfo/discuss
