Hi Matus,
Thanks for your answers.
Sounds like i'll need to tweak couple of places with a SQUID solution.
Last few days i managed to built a solution using a webserver
(aolserver) which can act in on of two modes for different url's. The
two modes, are proxy which directly passes the client's request to
backend server. The other mode is store-and-forward, where it stores
the request for it to be processed by messaging module.
best regards,
Jamshed
On 19 Feb 2007, at 11:02, Matus UHLAR - fantomas wrote:
On 16.02.07 20:34, Jamshed Qureshi wrote:
I have a third party http frontend who is contacted by 5000 clients
every morning. Server is not able to serve them and after a while it
crashes. I need to filter incoming request based on requested url and
then store them. At the same time return http 200 to those machines.
Mainly i have two issues:
1. Is it possible to configure SQUID to filter incoming request based
on url.
by using an ACL, yes
2. store those requests in some file.
by using some URL-redirector, yes.
3. forward them to back-end server at some later time.
this can be done by some external job running out of squid (e.g. cron)
--
Matus UHLAR - fantomas, uhlar@xxxxxxxxxxx ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
The early bird may get the worm, but the second mouse gets the cheese.
