can't access https but http works fine through route-map ->squid proxy
Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
you can't proxy SSL traffic like that. You're taking a client that expects to perform an SSL handshake and smooshing it head first into a server that is expecting an HTTP request. That won't work.
Stop trying to transparently proxy web traffic. is it NOT the magical wonder solution you hope it is. Configure your clients to explicitly use the proxy and you'll then find HTTPS proxying very simple.
I thought to use route-map because there are 200 pc and can't set manually on each of them and if there is any problem with proxy can't unset also manually in browser. Where is the difference when we set in browser and when we set via route-map?
is there any other possibility to do it?
because which I want to do is, to prevent some https and http sites and to allow some others.
What you can also do is use a proxy.pac file held on a central server and deployed by dns or dhcp to make all browsers automatically pick it up. that's a handy way to not actually have todeploy files to all the PCs. You could just send an email to everyone to say "make sure your browser is set to auto discover proxy details" or even "tell your browser to use http://localserver/proxy.pac"
I don't understand why route-map (as in the ios feature??) would have any interaction with SSL / Non-SSL requests, that's just IP level packet redirection.