Re: [squid-users] Can cache_peer be localhost?

2018-02-17 Thread Yuri
18.02.2018 01:13, Matus UHLAR - fantomas пишет: > On 18.02.18 00:05, Yuri wrote: >> May be, assumed to forwarding to parent proxy(-es)? > > according to original post, it's different port configured on the same > squid > instance. Ewww. it seems like looping. > >> 17.02.2018 23:22, Matus

Re: [squid-users] Can cache_peer be localhost?

2018-02-17 Thread Matus UHLAR - fantomas
On 18.02.18 00:05, Yuri wrote: May be, assumed to forwarding to parent proxy(-es)? according to original post, it's different port configured on the same squid instance. 17.02.2018 23:22, Matus UHLAR - fantomas пишет:  client -> Squid (3129) -> Squid (3128) -> Squid (3128) ... repeat forever

Re: [squid-users] Can cache_peer be localhost?

2018-02-17 Thread Yuri
May be, assumed to forwarding to parent proxy(-es)? 17.02.2018 23:22, Matus UHLAR - fantomas пишет: >>>  client -> Squid (3129) -> Squid (3128) -> Squid (3128) ... repeat >>> forever. > > On 17.02.18 10:45, Peng Yu wrote: >> Is there a way to configure squid so that anything goes to 3128 will >>

Re: [squid-users] Forward proxy: TLS connections to server

2018-02-17 Thread Yuri
IM, which is uses HTTP-similar sessions bootstrap, requires special investigation and custom configuration in case of goes via forwarding proxy. 17.02.2018 22:58, ninadmnaik пишет: > Thanks for the quick reply Yuri. > > "Note that these are not 'https' requests. Just plain socket connections." >

Re: [squid-users] Can cache_peer be localhost?

2018-02-17 Thread Matus UHLAR - fantomas
client -> Squid (3129) -> Squid (3128) -> Squid (3128) ... repeat forever. On 17.02.18 10:45, Peng Yu wrote: Is there a way to configure squid so that anything goes to 3128 will directly go outside of the machine instead of going back to 3128 again, yet still let 3129 be forwarded to the local

Re: [squid-users] Forward proxy: TLS connections to server

2018-02-17 Thread ninadmnaik
Thanks for the quick reply Yuri. "Note that these are not 'https' requests. Just plain socket connections." Maybe this wasn't statement wasn't entirely correct. We are using the 'connect' method to talk to squid proxy. And squid proxy is able to connect to the remote xmpp server. It's just that t

Re: [squid-users] Can cache_peer be localhost?

2018-02-17 Thread Peng Yu
> client -> Squid (3129) -> Squid (3128) -> Squid (3128) ... repeat forever. Is there a way to configure squid so that anything goes to 3128 will directly go outside of the machine instead of going back to 3128 again, yet still let 3129 be forwarded to the local 3128 in the round-robin fashion?

Re: [squid-users] Forward proxy: TLS connections to server

2018-02-17 Thread Yuri
17.02.2018 21:44, ninadmnaik пишет: > Hello, > We need to communicate with a xmpp server over TLS connections. Now, we know > that our app can open a TLS connection to Squid. But can Squid initiate a > TLS connection to the xmpp server? Only if it goes over HTTP/HTTPS port. With some difficults

[squid-users] Forward proxy: TLS connections to server

2018-02-17 Thread ninadmnaik
Hello, We need to communicate with a xmpp server over TLS connections. Now, we know that our app can open a TLS connection to Squid. But can Squid initiate a TLS connection to the xmpp server? Our App (TLS socket connection)---> Squid (Can this be TLS connection?)> XMPP server If it

Re: [squid-users] Transition from squid3.5 to squid4; ciphers don't work anymore, ERROR: Unknown TLS option SINGLE_DH_USE

2018-02-17 Thread Amos Jeffries
On 18/02/18 03:10, Amos Jeffries wrote: > > On 18/02/18 02:39, chiasa.men wrote: >> >> I could solve the "no ciphers available" by appending >> "TLS13-AES-256-GCM-SHA384" to the ciphers. >> >> But the log shows the use of "ECDHE-ECDSA-AES256-GCM-SHA384" >> >> Why is that cipher relevant if its not

Re: [squid-users] squid -k rec , seems has problem with ram leakage ?

2018-02-17 Thread Amos Jeffries
On 18/02/18 02:38, --Ahmad-- wrote: > Hi Amos ,  > > so you mean that the extra Ram usage is from the instance when it loaded > with traffic ? Probably. It is small enough in size to be from that. Detailed inspection is necessary to know for sure. > > will that stay even if i have cache men 0

Re: [squid-users] Transition from squid3.5 to squid4; ciphers don't work anymore, ERROR: Unknown TLS option SINGLE_DH_USE

2018-02-17 Thread Amos Jeffries
On 18/02/18 02:39, chiasa.men wrote: > > I could solve the "no ciphers available" by appending > "TLS13-AES-256-GCM-SHA384" to the ciphers. > > But the log shows the use of "ECDHE-ECDSA-AES256-GCM-SHA384" > > Why is that cipher relevant if its not used? > The squid.conf cipher= are just strin

Re: [squid-users] Transition from squid3.5 to squid4; ciphers don't work anymore, ERROR: Unknown TLS option SINGLE_DH_USE

2018-02-17 Thread Amos Jeffries
On 13/02/18 02:29, chiasa.men wrote: > Hi I tried squid4. > > Squid Cache: Version 4.0.23 > This binary uses OpenSSL 1.1.1-dev xx XXX > > Before, I used: > Squid Cache: Version 3.5.27 > This binary uses OpenSSL 1.0.2g 1 Mar 2016 > > Some of the config directives changed: > E.g. > sslpro

Re: [squid-users] squid -k rec , seems has problem with ram leakage ?

2018-02-17 Thread --Ahmad--
Hi Amos , so you mean that the extra Ram usage is from the instance when it loaded with traffic ? will that stay even if i have cache men 0 and and cache deny all and disabling all HDD caching ? is there anything can i do ? or leave it s it is ? cheers > On Feb 17, 2018, at 3:20 PM, Amo

Re: [squid-users] Transition from squid3.5 to squid4; ciphers don't work anymore, ERROR: Unknown TLS option SINGLE_DH_USE

2018-02-17 Thread chiasa.men
Am Samstag, 17. Februar 2018, 14:28:04 CET schrieb chiasa.men: > Am Montag, 12. Februar 2018, 14:29:09 CET schrieb chiasa.men: > > Hi I tried squid4. > > > > Squid Cache: Version 4.0.23 > > This binary uses OpenSSL 1.1.1-dev xx XXX > > > > Before, I used: > > Squid Cache: Version 3.5.27 > >

Re: [squid-users] Transition from squid3.5 to squid4; ciphers don't work anymore, ERROR: Unknown TLS option SINGLE_DH_USE

2018-02-17 Thread chiasa.men
Am Montag, 12. Februar 2018, 14:29:09 CET schrieb chiasa.men: > Hi I tried squid4. > > Squid Cache: Version 4.0.23 > This binary uses OpenSSL 1.1.1-dev xx XXX > > Before, I used: > Squid Cache: Version 3.5.27 > This binary uses OpenSSL 1.0.2g 1 Mar 2016 > > Some of the config directives c

Re: [squid-users] squid -k rec , seems has problem with ram leakage ?

2018-02-17 Thread Amos Jeffries
On 18/02/18 00:57, --Ahmad-- wrote: > hi amos  > > i didnt use the version 3.5.22 > >  but long time I’m using the 3.5.22 and its fine  > > the new thing is I’m using like 100 squid instances . > > and  hourly i have cron to change and update squid  > > so i just make rec option instead of hav

Re: [squid-users] squid -k rec , seems has problem with ram leakage ?

2018-02-17 Thread --Ahmad--
hi amos i didnt use the version 3.5.22 but long time I’m using the 3.5.22 and its fine the new thing is I’m using like 100 squid instances . and hourly i have cron to change and update squid so i just make rec option instead of having session drop . i don’t have exact mount of statistics

Re: [squid-users] How to combine two proxies into one?

2018-02-17 Thread Amos Jeffries
On 17/02/18 14:37, Peng Yu wrote: > On Thu, Feb 15, 2018 at 3:31 AM, Amos Jeffries wrote: >> >> BUT, since neither of them was actually a reverse-proxy the answer of >> how to merge a reverse-proxy and a forward-proxy would be quite different. > > I finally figure a configure that works. localhost

Re: [squid-users] Can cache_peer be localhost?

2018-02-17 Thread Amos Jeffries
On 17/02/18 15:05, Peng Yu wrote: > Hi, I have the following configuration. When I access port 3129 and it > is localhost's turn in the round-robin, then the access will fail. Is > there a way to make it work? > > $ grep -v '^#' squid.conf|grep -v '^$' ... > http_port 3128 This port receives loca

Re: [squid-users] squid -k rec , seems has problem with ram leakage ?

2018-02-17 Thread Amos Jeffries
On 17/02/18 10:53, --Ahmad-- wrote: > hey folks > > i have a Multi instances in squid and i run them and keep use(( -k rec))) > option > "rec" as in the first characters of the "-k reconfigure" option? That will only update the running Squid with new config file settings. Sometimes that ca