Need help setting up a Squid proxy 4.17 as per requirements
Budget: $30 – $250 USD
I need a skilled freelancer to set up a Squid proxy 4.17 for me on Linux (OpenWrt 22.03.4 based on Linux Kernel 5.10) with requirements:
1. Set up separate Squid (must run under different users) instances on each WAN interface (each instance must be with its own configuration file);
2. All instances must use shared caching on SSD or on remote server (need to show how to set it up in the configuration file for both scenarios);
3. Main function of all configurations is the SSL (with SSL bumping) caching of static content, need to do configuration without importing any certificates in browser (static content must be cached without any warnings for valid HTTPS sites in browser, that connected through Squid proxy to remote HTTPS sites);
4. Each Squid instance must provide an 4 HTTP(s) proxy ports with multiple users basic authorization (4 ports and 4 users for each instance) for other services/clients to connect to it (need to separately store logins and passwords for each instance of squid);
5. If needed — answer on additional questions with Squid configuration.
In general, i am need example of Squid 4.17 with 2 working configs (4 ports and 4 unique users for each config) for two WAN interfaces, that will use shared cache for static content of https sites, and provide HTTP(s) proxy for clients connection, there should be no warnings on client browsers that the connection is not secure (and DO NOT import any certificates in clients browsers).
If you read carefully all project, and understand what to do — write in your bid:
"I can do Squid cache with SSL without warnings".
1. Set up separate Squid (must run under different users) instances on each WAN interface (each instance must be with its own configuration file);
2. All instances must use shared caching on SSD or on remote server (need to show how to set it up in the configuration file for both scenarios);
3. Main function of all configurations is the SSL (with SSL bumping) caching of static content, need to do configuration without importing any certificates in browser (static content must be cached without any warnings for valid HTTPS sites in browser, that connected through Squid proxy to remote HTTPS sites);
4. Each Squid instance must provide an 4 HTTP(s) proxy ports with multiple users basic authorization (4 ports and 4 users for each instance) for other services/clients to connect to it (need to separately store logins and passwords for each instance of squid);
5. If needed — answer on additional questions with Squid configuration.
In general, i am need example of Squid 4.17 with 2 working configs (4 ports and 4 unique users for each config) for two WAN interfaces, that will use shared cache for static content of https sites, and provide HTTP(s) proxy for clients connection, there should be no warnings on client browsers that the connection is not secure (and DO NOT import any certificates in clients browsers).
If you read carefully all project, and understand what to do — write in your bid:
"I can do Squid cache with SSL without warnings".