Re: [squid-users] Non-Transparent HTTP+HTTP Proxy

2019-09-16 Thread Matus UHLAR - fantomas
On 16.09.19 05:45, sknz wrote: [Updated] I'm trying to configure Squid 3.5.3 for access controller/captive portal last few days. #1 For this config, on client device: *URL could not be retrieved - Invalid Url* http_port 3128 #2 Squid log throws an Error - No forward port http_port 3128 interce

Re: [squid-users] Non-Transparent HTTP+HTTP Proxy

2019-09-16 Thread sknz
[Updated] I'm trying to configure Squid 3.5.3 for access controller/captive portal last few days. #1 For this config, on client device: *URL could not be retrieved - Invalid Url* http_port 3128 #2 Squid log throws an Error - No forward port http_port 3128 intercept #3 On client device: *UR

Re: [squid-users] Non-Transparent HTTP+HTTP Proxy

2019-09-16 Thread sknz
I'm trying to configure Squid 3.5.3 for access controller/captive portal last few days. #1 For this config, on client device: *URL could not be retrieved - Invalid Url* http_port #2 Squid log throws an Error - No forward port http_port 3128 intercept #3 On client device: *URL could not be

Re: [squid-users] Non-Transparent HTTP+HTTP Proxy

2019-09-16 Thread Matus UHLAR - fantomas
On 16.09.19 03:27, sknz wrote: So my straight-forward goal is here, i. Non-transparent proxy ( transparent doesn't work with captive portal ) if you mean, explicit proxy (client must explicitly configure it), not an intercepting proxy (http connections are redirected to proxy, browser doesn't

Re: [squid-users] Non-Transparent HTTP+HTTP Proxy

2019-09-16 Thread sknz
So my straight-forward goal is here, i. Non-transparent proxy ( transparent doesn't work with captive portal ) ii. LOG HTTP and HTTPS traffic ( for HTTPS hostname will do ) iii. Without issuing any certificate in client device Is it possible with Squid 3.5? -- Sent from: http://squid-web-prox