Hi,
I accidentally access squid-cache.org and get 403 Forbidden error,
and am wondering why NOT redirect to WWW.squid-cache.org
automatically?
I'm sorry if it's intention.
~Ned
___
squid-users mailing list
squid-users@lists.squid-cache.org
Hi,
The http://www.squid-cache.org/ domain web site is working fine.
We have accessed the site a min ago.
Regards,
ViSolve Squid
On 9/30/2014 1:47 PM, Neddy, NH. Nam wrote:
Hi,
I accidentally access squid-cache.org and get 403 Forbidden error,
and am wondering why NOT redirect to
I had pointed this out few months back but I suppose it was not
corrected or not considered necessary.
Amm.
On 09/30/2014 02:15 PM, Дмитрий Шиленко wrote:
without www.* -- Forbidden You don't have permission to access /
on this server.
Visolve Squid писал 30.09.2014 11:42:
Hi,
The
without www.* -- Forbidden You don't have permission to access / on
this
server.
Some browsers (Chrome?) will help by prepending www on the front for you...
if you type just squid-cache.org it will turn it into
http://www.squid-cache.org and you won't see the problem. Maybe this only
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/30/2014 05:11 AM, Victor Sudakov wrote:
Can you share the basic cache manager requests statistics and the
up time for the service? (mgr:info)
This would give us a basic idea of the load\requests needed to
reproduce it.
I am not Steve
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hey Alejandro,
Can I ask where in the site have you taken this code from?
Using php as a helper is not such a good choice due to couple issues
it has with squid stdin\stdout emulation.
You'd better use perl\python\ruby\other then php unless you
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Eliezer Croitoru wrote:
Attaching two cachemgr reports: right after squid restart and
several hours later (grown to 816M in SIZE).
I am not very good at calculating what I do not know how to yet!
What I do understand is that Cumulative allocated
When i use squid and get headers like,
HTTP/1.1 301 Moved Permanently
Location: http://www.hotmail.com/
squid ends up in a endless loop.
ERR_TOO_MANY_REDIRECTS
Some say to use u url_rewriter or location_rewrite, but how and where
to read more about this.
or is it that simple that squid can't
On 29.09.14 13:39, Eliezer Croitoru wrote:
Hey Steve,
Can you share the basic cache manager requests statistics and the up
time for the service?
(mgr:info)
This is with 8 workers and was restarted this morning, about 6 hours
ago. As you can see, it's using about 5GB at the moment - as
It's possible to redirect all ports to squid ? thru iptables ?
For example port 25 smtp,143 imap, etc...
Can squid handle that. In transparent mode.
smime.p7s
Description: S/MIME cryptographic signature
___
squid-users mailing list
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Indeed using SSL-BUMP it's possible but(a bit but)..
It will not be able to handle non http\https traffic just like that.
It will require more then just squid setup and it might be a better
idea to find a better solution for you rather then using
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 09/30/2014 08:30 PM, Leonardo Rodrigues wrote:
Other protocols, SMTP, IMAP, POP3, etc etc etc, cannot be handled
by squid.
They cannot be interpreted but can be handled with a none rule for
ssl bump.
Eliezer
-BEGIN PGP SIGNATURE-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Squid rejects connections made with https://sohnen-moe.com:2083/. I
had thought that the ACL acl Safe_ports port 1025-65535 was
sufficient. Obviously not.
What should I change to allow connections with port 2083?
- [ Excerpts from the conf:
13 matches
Mail list logo
