Here is the output as you said
--2010-06-04 18:45:53-- http://localhost:8080/
Resolving localhost... 127.0.0.1
Connecting to localhost|127.0.0.1|:8080... connected.
HTTP request sent, awaiting response... 200 OK
Length: 2714 (2.7K) [text/html]
Saving to: `index.html'
100%[==============================================================================================================================>] 2,714 --.-K/s in 0s
2010-06-04 18:45:53 (185 MB/s) - `index.html' saved [2714/2714]
Apart from what you said here is what I did
ssh -L 8080:localhost:8080 root@servername
and in browser tested
what I is being served and makes my site slow.
By default some how this is the only thing which is being served to the users
on internet also.
So the site is slow.
Here is a snapshot
of what I just said
and to prove what makes it slow I again loaded the website
in Chrome Developer Tools pressed Control+Shift+I
and was able to record the time page elements were taking to load they showed some css or jquery took more than 100ms
is another snapshot.
What is happening is eduCommons is using a server Zope.
Zope is running on port 8080 behind an Apache running on port 80.
The Virtual Host Manager doesn't do anything unless it sees one of the following special path elements in a URL: VirtualHostBase sets the protocol and host, while VirtualHostRoot sets the path root.
In the Proxy Pass directive I am passing the url to an internal IP
where I can access the website on LAN like this
some how the first snapshot
is what is being served to the users on internet and that itself is taking time.
So the website is slow.
While on LAN where I can locally browse the website I am directly getting the response from Zope.
So it is not noticeable on LAN.