On 08/06/17 02:04, joseph wrote:
right
lets say i have obj with this header
if server send the same obj with different Set-Cookie value that will be
MISS i was refairing to this
not to the vary if it has cookie sorry if i did not explain it correctly
Cookie(s) have nothing to do with MISS
On 06/07/2017 03:37 AM, Jason Chiu wrote:
> 1495699856.074 0 192.168.95.81 TCP_DENIED/200 0 CONNECT 127.0.0.1:3129
> *Need to adjust which part of the settings?*
If that connection is really trying to connect to 127.0.0.1:3129 from
Squid point of view, then your interception setup is
On 08/06/17 01:00, joseph wrote:
so if the server send same obj with new Cookie it will be miss since the
Cookie dose not match in cached obj
No, the Vary header does not say Cookie is part of the variance AFAICT.
Just URL plus Accept-Encoding.
The Cookie/Set-Cookie being accurate is
On 08/06/17 03:28, Adiel Plasencia Herrera wrote:
Hello,
They would help me with a configuration of my squid that I want to
implement.
My proxy passes all traffic to a parent proxy and I want clients to
connect to my proxy via https.
Can you help me how to implement the connection to my
On 07/06/17 22:54, Ишаяhу Ластов wrote:
I use squid on freebsd 10.3. When I set proxy adress in web brouser, I
can't attach files to mail on mail.ru. Whithout proxy it works. In
access.log there are no errors. In cache.log I've got:
|2017/05/29 21:12:16 kid1| local=217.151.68.36:34572
On 07/06/17 21:42, joseph wrote:
is Set-Cookie: saved in cached file as well ?? amos
Yes it is. The header on the cached object only gets removed on delivery
to a client.
Squid does not comply with the Cookie specifications in this regard.
With the extra wrinkle that the mandatory
Hello,
They would help me with a configuration of my squid that I want to
implement.
My proxy passes all traffic to a parent proxy and I want clients to
connect to my proxy via https.
Can you help me how to implement the connection to my proxy via
https?
To better
On 07/06/17 13:00, Михаил wrote:
Hi everybody!
Sometimes i get in cache.log this message:
"CacheManager::ParseUrl: action 'digestauthenticator' not found"
Tell me what it means?
For some reason the Squid process answering a manager HTTP(S) request
does not have the Digest authentication
On 07/06/17 12:13, Ivan Larionov wrote:
Hi!
We recently updated from squid v2 to v3 and now see huge increase in
connections in TIME_WAIT state on our squid servers (verified that
this is clients connections).
The biggest change between 2.7 and 3.5 in this area is that 2.7 was
HTTP/1.0
I use squid on freebsd 10.3. When I set proxy adress in web brouser, I can't
attach files to mail on mail.ru. Whithout proxy it works. In access.log there
are no errors. In cache.log I've got:
2017/05/29 21:12:16 kid1| local=217.151.68.36:34572 remote=217.69.139.216:443
FD 44 flags=1:
is Set-Cookie: saved in cached file as well ?? amos
--
View this message in context:
http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-issue-of-caching-the-m3u8-file-tp4682674p4682714.html
Sent from the Squid - Users mailing list archive at Nabble.com.
I also tested the following cases
test case 1:
add the following settings in squid.conf
acl bumpedPorts myportname 3129
http_access allow CONNECT bumpedPorts
test results: ssl bump is failed
1. access.log no record
2. web browser has been waiting , no response
I had a FreeBSD 9.1 bridge (em0, em1) environment,
Use "pf rdr to" redirect HTTPS (port 443) packets to squid (squid 127.0.0.1:
3129)
Squid *3.3.11* ssl bump is OK.
The following is the setting of squid 3.3.11
Squid Cache: Version 3.3.11-20140220-r12672
Configure options: '--prefix = / usr /
Hi Ivan,
On Tue, Jun 06, Ivan Larionov wrote:
> We recently updated from squid v2 to v3 and now see huge increase in
> connections in TIME_WAIT state on our squid servers (verified that this is
> clients connections).
I can confirm that since 3.5.22 to our ICAP scanners.
with 3.5.21 we had no
14 matches
Mail list logo
