Search squid archive
Reverse proxy setup forwarding HTTP-only clients to HTTPS-only backend server
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Reverse proxy setup forwarding HTTP-only clients to HTTPS-only backend server
- From: Tapio Niemi <tapio.niemi@xxxxxxxxx>
- Date: Fri, 11 Mar 2011 16:24:49 +0200
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.15) Gecko/20110303 Thunderbird/3.1.9
Hi all,
I'm new to squid and proxying in general, and I'm wondering if squid or
any other proxy software by that matter is the right tool for the setup
I need to do.
Here's my situation. I have a HTTPS-only server on public internet,
which requires client certificate authentication from all connections.
(On apache terms, it's configured "SSLVerifyClient require"). Lets' call
it server X.
On a private, safe network (192.168.x.x style) I have hundreds of
workstations that need to access server X. However, installing X.509
client certificates on all these workstations is a great administrative
burden.
So my intention is to put a reverse proxy server on the private network
that accepts HTTP-connections from the private network, has a valid
X.509 client certificate installed and uses this certificate to talk to
server X using HTTPS on behalf of all the clients in the private address
space.
So, is this possible? And if so, I would be grateful to be pointed on
some documentation where I can get started.
Thanks,
Tapio
[Index of Archives]
[Linux Audio Users]
[Samba]
[Big List of Linux Books]
[Linux USB]
[Yosemite News]