Squid Cache: Version 3.1.12
configure options: '--prefix=/usr' '--sysconfdir=/etc/squid'
'--bindir=/usr/sbin' '--sbindir=/usr/sbin' '--localstatedir=/var'
'--libexecdir=/usr/sbin' '--datadir=/usr/share/squid'
'--mandir=/usr/share/man' '--libdir=/usr/lib64'
'--sharedstatedir=/var/squid'
Hello,
ca y est je vends ma voiture, voilà l'annonce :
http://www.leboncoin.fr/voitures/603661288.htm
beaucoup de monde me répond pour envoyer la bête en Afrique, mais si
je peux faire un(e) heureux(se) en France et conclure l'affaire sans
emmerdement ça m'arrange ! faites donc circuler.
Cdlt
Ok, so what should I do if I want to pass SSH requests through squid?
On 01/13/2014 06:28 AM, m.shahve...@ece.ut.ac.ir wrote:
Which protocols does squid not support exactly?
In the context of this discussion, Squid officially supports HTTP
protocol [optionally encrypted using SSL or TLS]
On Wednesday 15 January 2014 at 14:04:19, m.shahve...@ece.ut.ac.ir wrote:
Ok, so what should I do if I want to pass SSH requests through squid?
Why would you want to do this, or indeed expect it to be possible?
What benefits from passing SSH through Squid so you expect to get, instead of
just
I want to pass all traffics through squid not only traffics are received
on port 80 and handling them in some ways. Now when I am doing so SSH
requests freeze without any response!
On Wednesday 15 January 2014 at 14:04:19, m.shahve...@ece.ut.ac.ir wrote:
Ok, so what should I do if I want to
If your SSH client can use a HTTPS proxy, than it will probably
work without major changes, as connections will be proxied as CONNECT
ones. In the case of CONNECT method, squid already works almost as a
passthrough proxy.
If your SSH client cannot use a HTTPS proxy, than probably
Em 15/01/14 11:04, m.shahve...@ece.ut.ac.ir escreveu:
Ok, so what should I do if I want to pass SSH requests through squid?
using an SSH client that can proxy requests through an HTTP/HTTPS
proxy should do it. If your client cant do that, than it probably wont
be possible as squid does
wonder why there are popups at all. or popups at all. NTLM should work without
any popups.
which browser do you use? IE?
could you try to discard the group-check auth?
we are using NTLM but everyone is allowed, after authentication. so we do not
use external_acl_type.
we only use
acl
Hallo, m.shahverdi,
Du meintest am 15.01.14:
I want to pass all traffics through squid not only traffics are
received on port 80 and handling them in some ways.
Sorry - I can't see any benefit in that desired configuration.
Viele Gruesse!
Helmut
So what do you mean by an SSH client that can proxy requests through an
HTTP/HTTPS proxy exactly?
Em 15/01/14 11:04, m.shahve...@ece.ut.ac.ir escreveu:
Ok, so what should I do if I want to pass SSH requests through squid?
using an SSH client that can proxy requests through an
Hi,
amazingly IE11 works perfect. Absolutely no HEAD-request appears in Squid
Logs and the video loads in seconds.
But this is no real solution for our IE9 / IE10 problem, because we are
forced to use IE10 (or IE9) because we must use some web applications which
are not supported with IE11 yet.
Hi,
Maybe what you are trying to achieve here is a combined proxy and firewall.
That could do; All HTTP traffic would be handled by Squid and all other traffic
filtered for example by iptables and just routed (not proxied) through the
server. These can be combined into a single server.
Em 15/01/14 12:06, m.shahve...@ece.ut.ac.ir escreveu:
So what do you mean by an SSH client that can proxy requests through an
HTTP/HTTPS proxy exactly?
i mean exactly what i wrote ... if you have an SSH client that can
proxy requests through an HTTP/HTTPS proxy, than you can use SSH
I use Squid 3.1.19. I have four squid boxes. All of them got direct Internet
Access. To share the diskcache of each Proxy, I configure them as siblings to
each other.
On Squid A:
cache_peer B sibling 8080 3130 proxy-only
cache_peer C sibling 8080 3130 proxy-only
cache_peer D sibling 8080 3130
Classification: UNCLASSIFIED
Caveats: NONE
We are running Squid 2.7 on a Windows Server 2003 machine. With a few
different HTTPS URL's we are getting an instantaneous This page can't be
displayed in Internet Explorer, doesn't matter what version of IE. In
Mozilla Firefox we get the connection has
We are running Squid 2.7 on a Windows Server 2003 machine. With a few
different HTTPS URL's we are getting an instantaneous This page can't be
displayed in Internet Explorer, doesn't matter what version of IE. In
Mozilla Firefox we get the connection has timed out . Doesn't even think
about it.
Classification: UNCLASSIFIED
Caveats: NONE
Sir,
No that is not the same issue. Some HTTPS sites work, some don't. The
browser does not even try to think about a response, just throws
the This page can't be displayed message in IE. And outr proxy is the only
means for Internet access so we can't
So it looks like squid3.1.12 does not handle HEAD properly. Having a short
glance at the old squid bugs, I did not see anything directly relevant to
this. Anyway, as it is an old version, no bug fixes will be done, I guess.
So I would suggest you to upgrade at least to very last 3.1.xx and check
Although being a fan of MS, I would assume a problem of
squid2.7/Windows-specific.
Because I still have several squid2.7/ubuntu running, and can not remember
such a problem for my Windows-users.
But I am using persistent server-conns with very last squid2.7
--
View this message in context:
Hi All,
I know, according to wiki
(http://wiki.squid-cache.org/Features/StoreID) ICP HTCP are not
supported. “URL queries received from cache_peer siblings are not
passed through StoreID helper. So the resulting store/cache lookup
will MISS on URLs normally alterd by StoreID.”
Still, in lab
Hi, after various test get work. This problems is head with option
cache-control=no-cache for example.
My doubt is, its possible alter the head for caching?
I trying using the option cache allow all but website with option
cache-control not worked.
Regards
On 01/06/2014 12:03 AM, Eliezer
Thanks for yours tips.
But I figure out the issue other way. I have done roll back to my old
machine what has squid 2.6 version so all it's working
2014/1/15 Rietzler, Markus (RZF, SG 324 / RIETZLER_SOFTWARE)
markus.rietz...@fv.nrw.de:
wonder why there are popups at all. or popups at all.
Interesting question Did you compare this behaviour to squid2.7 using
storeurl ?
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/ICP-and-HTCP-and-StoreID-tp4664307p4664310.html
Sent from the Squid - Users mailing list archive at Nabble.com.
Classification: UNCLASSIFIED
Caveats: NONE
Just curious that if there is an order that Squid goes in to match a site in
the allowed sites
ACL. Top down??
...Alan
***
* Alan Raczek *
* Principal Network Engineer *
*
Hello together,
I'm new on this list therefore I want to introduce myself shortly. My
Name is Christian and I'm working in a IT department.
Currently I'm setting up a squid3 (3.1.20-2.2) proxy connected with the
MS ActiveDirectory. Kerberos, NTLM and Basic authentication are already
working
On Wed, Jan 15, 2014 at 8:35 PM, babajaga augustus_me...@yahoo.de wrote:
Interesting question Did you compare this behaviour to squid2.7 using
storeurl ?
Nope. I just tried 4.3.2. Same result - both UDP and TCP requests go
with altered URLs.
On 2014-01-16 06:54, Usuário do Sistema wrote:
Thanks for yours tips.
But I figure out the issue other way. I have done roll back to my old
machine what has squid 2.6 version so all it's working
Perhapse instead of rolling backwards to 2.7 you could roll forwards and
try to the latest
Em 15/01/14 17:08, Raczek, Alan J CTR USARMY SEC (US) escreveu:
Just curious that if there is an order that Squid goes in to match a site in
the allowed sites
ACL. Top down??
Yeah ... basically top down.
http://wiki.squid-cache.org/SquidFaq/SquidAcl#Access_Lists
http_access allow|deny
Hi all
Trying
http://wiki.squid-cache.org/ConfigExamples/DynamicContent/Coordinator
Thanks :)
On 01/15/2014 12:02 PM, spiderslack wrote:
Hi, after various test get work. This problems is head with option
cache-control=no-cache for example.
My doubt is, its possible alter the head for
Hi,
I'm working with an SmpScale configuration with 2 workers defined. Each
worker has its own set of unique ports that it listens on. The
coordinator process doesn't have any http_port lines and generates tons
of these warnings:
ERROR: No forward-proxy ports configured
That doesn't seem
Actually, it is working. I found two mistakes in my config - a typo in
cache_peer_access directive and absence of 'allow-miss' in the
cache_peer definition.
After fixing them, inter cache communication is working only with
altered URLs but this still does the job:
- If UDP is MISS the originating
Hi Will,
Why are you giving each worker a unique set of ports? Typically you
configure one set of ports for all workers, and let the operating
system handle the underlying machinery of sharing the ports across the
worker processes.
See here for more details:
Nathan,
I used to run two squids on my servers which provide very similar, but
different services. I'm using SmpScale to simplify that configuration
into a single squid instance with 2 workers with slightly different
configurations. Honestly, there's one line difference, here's the top of
my
Hi All-
So I have a need to direct all web traffic through an IPSEC Tunnel to a
Squid Proxy server on the other end of the tunnel.
Sounds complicated but the concept is really easy however I am having
issues.
So let me gather as much info as I can:
*Location 1 Subnet:* 192.168.1.0/24
I noticed this could be complicated to the readers so I have drew up a Visio
Diagram to illustrate the flow so my question and issue is better
represented.
http://squid-web-proxy-cache.1019090.n4.nabble.com/file/n4664322/proxyissue.png
--
View this message in context:
On 2014-01-16 11:19, Will Roberts wrote:
Hi,
I'm working with an SmpScale configuration with 2 workers defined.
Each worker has its own set of unique ports that it listens on. The
coordinator process doesn't have any http_port lines and generates
tons of these warnings:
ERROR: No forward-proxy
On 01/15/2014 07:32 PM, Amos Jeffries wrote:
Something strange going on here with your Coordinator. That error is
only produced when actively generating a response that needs to embed
a URI for some resource served by Squid.
What is your coordinator doing that needs it to be aware of the
On Wed, Jan 15, 2014 at 08:40:16PM +0100, Christian Scholz wrote:
Is there anything other that I'm doing wrong? I am grateful for any
help.
Modify the settings in the browser. You need to turn off Enable
Integrated windows Authentication in the internet options.
--
Brett Lymn
This email
On 01/15/2014 07:06 AM, m.shahve...@ece.ut.ac.ir wrote:
So what do you mean by an SSH client that can proxy requests through an
HTTP/HTTPS proxy exactly?
One way to rephrase the above would be an SSH client that can be
configured to use an HTTP proxy as the next hop for SSH traffic (wrapped
in
On 01/15/2014 03:31 PM, Niki Gorchilov wrote:
Actually, it is working. [...] inter cache communication is working only with
altered URLs but this still does the job:
- If UDP is MISS the originating peer makes a TCP connection to
destination server and caches the result
- if UDP is HIT, the
Hey There,
Just note that the StoreID wiki was written during the design and testing.
I can think about a way to make squid do what you are talking about.
Eliezer
On 16/01/14 00:31, Niki Gorchilov wrote:
Actually, it is working. I found two mistakes in my config - a typo in
cache_peer_access
Good morning,
I've squid 3.3.11.xx on SLES11 SP3, all OK, but I often used squid
-k reconfigure after changing some configuration (adding forbiden
domains or so). But there is some problem - the command mentioned
above tell me some errors:
proxy:/etc/squid # squid -k reconfigure
squid:
42 matches
Mail list logo
