after checking the mod_accel I found out that it works only with http,
we need the cache & proxy to work both with http and https.
What was the reason for disabling https proxying & caching ?
Regards,
Roman
Igor Sysoev wrote:
On Thu, 21 Oct 2004, Roman Gavrilov wrote:
so what would you suggest I should do ?
implement it by myself ?
No, just look at http://sysoev.ru/mod_accel/
It's Apache 1.3 module as you need.
Igor Sysoev
http://sysoev.ru/en/
Bill Stoddard wrote:
Graham Leggett wrote:
Roman Gavrilov wrote:
In my opinion it would be more efficient to let one process complete
the request (using maximum line throughput) and return some busy
code to other identical, simultaneous requests until the file is
cached locally.
As anyone run into a similar situation? What solution did you find?
In the original design for mod_cache, the second and subsequent
connections to a file that was still in the process of being
downloaded into the cache would shadow the cached file - in other
words it would serve content from the cached file as and when it was
received by the original request.
The file in the cache was to be marked as "still busy downloading",
which meant threads/processes serving from the cached file would know
to keep trying to serve the cached file until the "still busy
downloading" status was cleared by the initial request. Timeouts
would sanity check the process.
This prevents the "load spike" that occurs just after a file is
downloaded anew, but before that download is done.
Whether this was implemented fully I am not sure - anyone?
It was never implemented.
--
-------------------------------------------------------------
I am root. If you see me laughing... You better have a backup!
|
