Hierony Manurung
Del Institute of Technology
Network Management
Pada Rabu, 22 April 2015 10:53, "squid-users-ow...@lists.squid-cache.org"
menulis:
- Pesan yang Diteruskan -
You are not allowed to post to this mailing list, and your message has
been automatically rejected.
Hi Fred,
I believe you're experiencing bug 3329:
http://bugs.squid-cache.org/show_bug.cgi?id=3329
Please try the patch that I have on there and see if that helps your issue.
Thank you,
Nathan.
On 17 April 2015 at 17:06, Stakres wrote:
> Hi All,
>
> Is anyone with an trick regarding this error
On 22/04/2015 7:30 p.m., snakeeyes wrote:
> Hmmm , cant u provide more info??
>
> I followed wiki
>
> http://wiki.squid-cache.org/ConfigExamples/Reverse/SslWithWildcardCertifiate
>
>
>
> but im still confused with certificates , if possible and don’t mind , could
> u tell me brief steps ?
On 22/04/2015 3:20 p.m., Alberto Perez wrote:
> Hi everyone,
>
> I am trying to setup cachemgr.cgi in my squid 3.5.2 box with nginx as web
> server. I was able to server first page of cachemgr but I can't get further
> this page, every credentials I try shows me the same page with no errors.
> (at
Hi everyone,
I am trying to setup cachemgr.cgi in my squid 3.5.2 box with nginx as web
server. I was able to server first page of cachemgr but I can't get further
this page, every credentials I try shows me the same page with no errors.
(attach image)
in my squid.conf file
cache_mgr alberto
cac
On 22/04/2015 1:31 p.m., Alex Samad wrote:
> I presume ssl proxy (peek/splice) doesn't work with client certs ?
peek/splice works with client certs.
peek to get the SNI and other publicly available details from TLS then
splice to pass that client data to the server is precisely the feature
design
On 22/04/2015 7:31 a.m., jaykbvt wrote:
> Hi Amos,
>
> Thanks for reply,
>
> I think I got ur point. If I understood correctly,
>
> if a user makes request for http://www.wikipedia.org then the client request
> header should look like:
>
> src: client_IP:random_port
> dst: wikipedia.org(ip_addr
I presume ssl proxy (peek/splice) doesn't work with client certs ?
Alex
___
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Said it was enough to understand. :)
I strictly recommend to start from here:
http://en.wikipedia.org/wiki/Public_key_infrastructure
22.04.15 13:30, snakeeyes пишет:
> Hmmm , cant u provide more info??
>
> I followed wiki
>
>
http://wiki.squi
Hmmm , cant u provide more info??
I followed wiki
http://wiki.squid-cache.org/ConfigExamples/Reverse/SslWithWildcardCertifiate
but im still confused with certificates , if possible and don’t mind , could u
tell me brief steps ?
thanks a lot for ur kind help
regards
From: squid
Hi Amos,
Thanks for reply,
I think I got ur point. If I understood correctly,
if a user makes request for http://www.wikipedia.org then the client request
header should look like:
src: client_IP:random_port
dst: wikipedia.org(ip_address):http
http request: http_request details. (host,url,etc..)
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Self-signed certificate is not suitable for use in a reverse proxy.
22.04.15 9:17, snakeeyes пишет:
> Hi
>
> I need to setup squid proxy as reverse proxy with https enabled
>
> I tried the bash script below and it run ok :
>
> ##
Hi
I need to setup squid proxy as reverse proxy with https enabled
I tried the bash script below and it run ok :
###
OPENSSL=/usr/bin/openssl
SSLDIR=/etc/mydlp/ssl
mkdir -p $SSLDIR || exit 1
rm -rf $SSLDIR/*
[ -e $SSLDIR/private.pem ] || $OPENSSL genrsa
On 22/04/2015 12:43 a.m., jaykbvt wrote:
> Hi Amos,
>
> Thanks for reply.
>
>
> local=*10.58.200.33:80 remote=10.210.83.249:*3375 FD 10 flags=33: accepted
>
>
> since squid is able to understand which client is requesting and following
> lines t
Hi Amos,
Thanks for reply.
local=*10.58.200.33:80 remote=10.210.83.249:*3375 FD 10 flags=33: accepted
since squid is able to understand which client is requesting and following
lines talks about request..
parseHttpReque
On 17/04/2015 12:51 p.m., iridium191 wrote:
> Thanks for your response Amos, it is much appreciated.
> The config is below, with comments excluded - we've done tests in the past
> to confirm it is not an open proxy and don't believe it is. Any commnts you
> may have would also be appreciated.
> Th
21.04.15 17:20, Amos Jeffries пишет:
On 21/04/2015 10:44 p.m., jaykbvt wrote:
Hi,
My squid is configured in interception mode with
http_port 3130
http_port 3129 intercept
squid is running with single network card. request comes from the Cisco ISG
and internet is also allowed from the same Cis
On 21/04/2015 10:44 p.m., jaykbvt wrote:
> Hi,
> My squid is configured in interception mode with
>
> http_port 3130
> http_port 3129 intercept
>
> squid is running with single network card. request comes from the Cisco ISG
> and internet is also allowed from the same Cisco ISG only.
I think th
So, what?
What's the problem?
21.04.15 16:44, jaykbvt пишет:
Hi,
My squid is configured in interception mode with
http_port 3130
http_port 3129 intercept
squid is running with single network card. request comes from the Cisco ISG
and internet is also allowed from the same Cisco ISG only.
IPt
after updating my second squid box to the latest squid 3.4.12 that have
solved ssl_crtd crashing problem
then i got the same assertion error that i had on my another squid box,
now both are damaged ,
also i uninstall latest 3.4.12 and reinstall the previous version and also
the same problem still h
Hi,
My squid is configured in interception mode with
http_port 3130
http_port 3129 intercept
squid is running with single network card. request comes from the Cisco ISG
and internet is also allowed from the same Cisco ISG only.
IPtables has been configured with following
squidip = 10.58.200.33
Hi,
In my experience, I came across the problem when Windows clients
access files on Windows servers (e.g. IIS, SharePoint, etc.) and the
server kept prompting user to enter user id and password.
Amos is right and my problem was with NTLM authentication. I solved
the problem with Squid version, e
On 16/04/2015 2:35 p.m., Jagannath Naidu wrote:
> anybody ???
> is it even possible ??
>
It seems the answer is "unknown".
FWIW: I did have one client see this same issue. It seemed to be NTLM
related (as in Office not doing NTLM properly), but they opted to go
with not passing the affected user
23 matches
Mail list logo
