zakaria rais ha scritto:
I mean , I want live just three port HTTP and HTTPS and FTP the other no .
Thank you
Then I think you should search for acl Safe_ports directives in
squid.conf and delete those that refere to the ports you want to close.
HTH
2010/7/26 Marcello Romani
Hello
I would like to bloque all the port in the squid and live just http and
https working , if someone know how we can do it I will be thankful .
Thank you
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/squid-port-tp2300195p2300195.html
Sent from the
squidACL ha scritto:
Hello
I would like to bloque all the port in the squid and live just http and
https working , if someone know how we can do it I will be thankful .
Thank you
Seems like you are trying to restrict internet access to websites. You
don't need squid for this. You need to
Hi Amos,
The problem is that in the web servers, will use that header for
statistics and for some sites, it will also use that field for
authentication purposes. In that cases the capability of modifying that
app is out of our scope, so we will have to think about other
solutions.
Thanks!
--
Hi Amos,
It is because I would like this name to be configurable on Squids side, to
be independent from the server app. I don't want to depend on the server app
so modifying the header could be nice. Any idea?
Best regards,
Sergio
--
View this message in context:
elsergio wrote:
Hi Amos,
It is because I would like this name to be configurable on Squids side, to
be independent from the server app. I don't want to depend on the server app
so modifying the header could be nice. Any idea?
XFF has nothing to do with the Server app. It's all about the
Hi,
Mmmm.. I see what you were talking about and seems to be logic. Thanks for
the help!
I have been thinking about one thing: I want to have some access statistics
for each server. For example, I want to have a list of all the http request
origin IP addresses that have reached each server.
Hi Amos,
It is possible to change the name of the header? Maybe it would be easier to
create a new one if possible. How can I configure it?
Thanks!
--
View this message in context:
http://www.nabble.com/SQUID-port-to-port-tp18578787p18632711.html
Sent from the Squid - Users mailing list
elsergio wrote:
Hi,
Mmmm.. I see what you were talking about and seems to be logic. Thanks for
the help!
I have been thinking about one thing: I want to have some access statistics
for each server. For example, I want to have a list of all the http request
origin IP addresses that have
Hi Amos,
It is possible to change the name of the header? Maybe it would be easier
to
create a new one if possible. How can I configure it?
What are you trying to do exactly?
You asked for the server to identify client requesting squid. Thats what
forwarded-for does. As common behavior in
Henrik Nordstrom-5 wrote:
On mån, 2008-07-21 at 15:19 -0700, elsergio wrote:
Hi,
Here comes another squid question:
It is possible to have a squid proxy working like this:
listening on port 80 and forward connection to ip1 on port 8080
listening on port 81 and forward connection to
elsergio wrote:
Henrik Nordstrom-5 wrote:
On mån, 2008-07-21 at 15:19 -0700, elsergio wrote:
Hi,
Here comes another squid question:
It is possible to have a squid proxy working like this:
listening on port 80 and forward connection to ip1 on port 8080
listening on port 81 and forward
Hi all,
I have been suggested this
http_port 80 81 #to make squid listen to the desired ports
One per line.
Do I have to do something like this?
http_port 80
acl all src 0.0.0.0/0.0.0.0
always_direct allow all
cache_peer ip1 parent 8080 0 no-query origin_server name=DS1
cache_peer_access
On Tue, Jul 22, 2008 at 07:01:42AM -0700, elsergio wrote:
I have been suggested this
http_port 80 81 #to make squid listen to the desired ports
One per line.
Do I have to do something like this?
http_port 80
acl all src 0.0.0.0/0.0.0.0
always_direct allow all
cache_peer ip1
Hi all,
I have been suggested this
http_port 80 81 #to make squid listen to the desired ports
One per line.
Do I have to do something like this?
http_port 80
acl all src 0.0.0.0/0.0.0.0
always_direct allow all
cache_peer ip1 parent 8080 0 no-query origin_server name=DS1
Hi,
Here comes another squid question:
It is possible to have a squid proxy working like this:
listening on port 80 and forward connection to ip1 on port 8080
listening on port 81 and forward connection to ip2 on port 8181
Both options at the same time.
I have seen that you can set several
On mån, 2008-07-21 at 15:19 -0700, elsergio wrote:
Hi,
Here comes another squid question:
It is possible to have a squid proxy working like this:
listening on port 80 and forward connection to ip1 on port 8080
listening on port 81 and forward connection to ip2 on port 8181
Yes. That's
Hello,
there is an internet application we want to use and i have some clients
who needs to connect to it.
Firewall is setup so that it can connect to thos ports, proxy server is
squid.
The internet application is using different ports, my proxy server
listens only to port 4480 (http traffic for
I have squid listening of multiople ports, is there a way to pass
which of these ports the client connected on to an external acl?
Ben
On Tue, 11 Oct 2005, Ben Sagal wrote:
I have squid listening of multiople ports, is there a way to pass
which of these ports the client connected on to an external acl?
Not implemented, but trivial to add. See src/external_acl.c.
I would suggest using the same names as used in the acl
20 matches
Mail list logo
