For some reason, I need to protect and also publish the internal DMZ webserver. I thought reverse proxying will fit in this circumstance.
So, after upgrading my squid into version 3.x, I modified squid.conf.
After some searching and testing, main configuration of reverse proxying will only need :
#———————————————–
acl all src 0.0.0.0/0.0.0.0
visible_hostname localhost
icp_access allow all
http_port 80 transparent
# hook the real webserver on port 80
cache_peer xx2.1xx.xx0.2xx parent 80 0 no-query originserver weight=1
http_access allow all
#———————————————–
The rest is just regular squid typical configuration..
In my chase, it’s worked ![]()
0 comments ↓
There are no comments yet...Kick things off by filling out the form below.
Leave a Comment