From: Emilio Casbas <ecasbas@unav.es>
To: dleangen@canada.com
Cc: netfilter@lists.netfilter.org
Subject: Re: [OT] URL rewriting
Date: Thu, 13 Oct 2005 11:28:39 +0200 [thread overview]
Message-ID: <434E28C7.8000801@unav.es> (raw)
In-Reply-To: <NEBBKBPLMLNABNADCIPAGEOCBIAB.dleangen@canada.com>
David Leangen wrote:
>Ok, this topic is now officially OT...
>
>
>
>>Better to use a HTTP proxy.
>>
>>
>>
>>>What do you recommend?
>>>
>>>
>>Well, Squid obviously, but then I am perhaps somewhat biased..
>>
>>
>
>
>Why do you recommend Squid? I am very interested.
>
>
Obvious ;-)
http://www.squid-cache.org/volunteers.html.
>I briefly checked out both, and this is what I concluded:
>
> - Squid seems more complicated to set up. Even after
> reading the docs, I still have no idea how to configure this.
>
>
http://www.squid-cache.org/Doc/FAQ/FAQ-15.html
> - I asked how to do this on the mailing list, but I guess my
> question was too basic and nobody was interested in
> replying
>
>
patience,
> - Squid can do LOTS of stuff, but all I want is a reverse proxy
>
>
http://www.squid-cache.org/Doc/FAQ/FAQ-20.html
> - I already have an Apache installation and I know how to use
> reverse proxying
>
>
>Despite this, I'm always interested in the "best" solution... I would indeed
>be very curious to know why you think Squid is the best choice.
>
>
>
My personal opinion is that.
I have using squid for three years ago in many environments
chain proxy, reverse proxy, ssl proxy, filtering proxy...
and i`m agree too with Henrik.
Thanks
Emilio C.
prev parent reply other threads:[~2005-10-13 9:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-12 7:07 [OT?] URL rewriting David Leangen
2005-10-12 21:04 ` Henrik Nordstrom
2005-10-12 23:09 ` [OT] " David Leangen
2005-10-13 9:28 ` Emilio Casbas [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=434E28C7.8000801@unav.es \
--to=ecasbas@unav.es \
--cc=dleangen@canada.com \
--cc=netfilter@lists.netfilter.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.