On 22/02/2016 12:39 a.m., Antony Stone wrote:
> On Sunday 21 February 2016 at 11:34:44, HackXBack wrote:
>
>> Bump links by extension files
>> and not by servername
>
> I'm still not at all sure I understand what you mean.
>
> Please give one example of what you want to do and explain why it wou
Also,
Whatsapp needs other ports open, 5223, 5228, 4244, 5242 and 5222.
Chico Venancio
Em 21/02/2016 16:33, "Antony Stone"
escreveu:
> On Sunday 21 February 2016 at 20:10:59, turgut kalfaoğlu wrote:
>
> > Thank you for your reply; there is nothing about SSL neither in iptables
> > nor in squid s
On Sunday 21 February 2016 at 20:10:59, turgut kalfaoğlu wrote:
> Thank you for your reply; there is nothing about SSL neither in iptables
> nor in squid settings now.
> It only intercepts port 80 requests..
So, does this mean that all browsers and similar clients are unable to access
any HTTPS
Thank you for your reply; there is nothing about SSL neither in iptables
nor in squid settings now.
It only intercepts port 80 requests..
There is nothing visible in squid's access.log nor the firewall logs of
the server when I click on an image to download in Whatsapp.
-turgut
_
On Sunday 21 February 2016 at 19:51:05, turgut kalfaoğlu wrote:
> Hi.. On my LAN's squid server, I redirect port 80 to local squid,
>iptables -t nat -A PREROUTING -s 192.168.2.0/24 -p tcp --dport 80 -j
> REDIRECT --to-port 3128
>
> and the squid speeds up and anonymizes the requests from the
Hi.. On my LAN's squid server, I redirect port 80 to local squid,
iptables -t nat -A PREROUTING -s 192.168.2.0/24 -p tcp --dport 80 -j
REDIRECT --to-port 3128
and the squid speeds up and anonymizes the requests from the LAN.
This works well for http, unfortunately I could not get https working
On Sunday 21 February 2016 at 12:56:03, secoonder wrote:
> My Firewall eth0: 192.168.1.180
> eth1:192.168.2.180
I'm guessing that eth0 is your route to the Internet, and eth1 points towards
the clients trying to use Squid?
> ip_forwarding enable and more /proc/sys/net/ipv4/ip_
Antony Thank you.
My Firewall eth0: 192.168.1.180
eth1:192.168.2.180
ip_forwarding enable and more /proc/sys/net/ipv4/ip_forward =1
iptables -t nat -A POSTROUTING -s 192.168.5.0/255.255.255.0 -o eth0 -j
MASQUERADE
This is no problem above it.The cilents could connect internet.
And
Hi Markus,
When you say authentication does not work, do you mean Kerberos
authentication or Kerberos and NTLM ? Can you add a -d for debug to the
Kerberos authentication helper and provide the log file messages ?
Can you also provide the content of the keytab ?
Regards
Markus
"Markus So
On Sunday 21 February 2016 at 11:34:44, HackXBack wrote:
> Bump links by extension files
> and not by servername
I'm still not at all sure I understand what you mean.
Please give one example of what you want to do and explain why it would be an
improvement over the standard method.
Thanks,
A
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Stupid idea.
21.02.16 16:34, HackXBack пишет:
> Bump links by extension files
> and not by servername
>
>
>
> --
> View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/bump-files-tp4676075p4676085.html
> Sent from the
Bump links by extension files
and not by servername
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/bump-files-tp4676075p4676085.html
Sent from the Squid - Users mailing list archive at Nabble.com.
___
squid-users
12 matches
Mail list logo
