On 25/06/2016 4:48 a.m., Bidwell, Christopher wrote:
> Hi all,
>
> I'm very new to squid and we are wanting to implement letsencrypt for our
> ssl certificates.
>
> Here's the scenario:
>
> We've got several frontend servers running squid that are caching from the
> backend systems.
Ok,
>
> i
On 25/06/2016 12:31 a.m., joe wrote:
> hi wen using ecap adapter
> ecap_enable on
> acl HTTP_STATUS_OK http_status 200
> loadable_modules /usr/local/lib/ecap_adapter_gzip.so
> ecap_service gzip_service respmod_precache ecap://www.vigos.com/ecap_gzip
> bypass=off
> adaptation_access gzip_service all
Hello Amos,
The Via from mine is:
Via:"http/1.1 fts110.flickr.bf1.yahoo.com (ApacheTrafficServer [cMs f ]),
http/1.1 r02.ycpi.ams.yahoo.net (ApacheTrafficServer [cMsSf ]), 1.1 qlproxy
(squid/3.3.8)"
Might it be the error when constructing via contents in squid? As it starts
with 1.1 while oth
On 25/06/2016 4:02 a.m., Yuri Voinov wrote:
>
> Be careful, guys. Via is reauired to HTTP by RFC.
>
As of RFC 7230 et al, it is officially now optional. Yay!
As of Squid-3.2 emitting HTTP/1.1, its use in preventing 1.1<->1.0
translation errors is greatly reduced. Yay!
It is still important to
On 25/06/2016 3:40 a.m., Ozgur Batur wrote:
> Hi Rafael, Yuri,
>
> Thank you very much, "via off" did the trick. It is probably a server
> specific issue as you said.
>
Hmm. What was the Via header emitted by your proxy?
There are some common misconfigurations that can lead to a broken Via
bein
On 25/06/2016 6:39 a.m., Bidwell, Christopher wrote:
> Hi all,
>
> Just curious if you could help me figure out what the equivalent of this
> apache rule would be for squid:
>
> RewriteRule ^/dyfi/?$ http://servername.com/data/dyfi/
> [R=301,L]
>
Below, with the comments descr
On 25/06/2016 6:27 a.m., Stefan Hölzle wrote:
> Hello,
>
> I'm having trouble configuring a forward proxy.
> My goal is the following:
> Only for one destination domain IPv6 should be used, otherwise IPv4.
This is not how the Internet Protocol (IP) works. If a domain is
advertising IPv6 addresses
Hi all,
Just curious if you could help me figure out what the equivalent of this
apache rule would be for squid:
RewriteRule ^/dyfi/?$ http://servername.com/data/dyfi/
[R=301,L]
___
squid-users mailing list
squid-users@lists.squid-cach
if i do with regex it work it bypass it
acl redirecturls url_regex -i \/snc\/api2
adaptation_access gzip_service allow HTTP_STATUS_OK !redirecturls
this preventing method dose not work
acl nomethod method POST
adaptation_access gzip_service allow HTTP_STATUS_OK !nomethod
--
View this message i
Hi all,
I'm very new to squid and we are wanting to implement letsencrypt for our
ssl certificates.
Here's the scenario:
We've got several frontend servers running squid that are caching from the
backend systems.
i.e. test.com -> 10.0.0.1, 10.0.1.1, 10.0.2.1 (all physically separated
from one a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Be careful, guys. Via is reauired to HTTP by RFC.
24.06.2016 21:40, Ozgur Batur пишет:
> Hi Rafael, Yuri,
>
> Thank you very much, "via off" did the trick. It is probably a server
specific issue as you said.
>
> Best Regards,
>
> On Fri, Jun 24,
Hi Rafael, Yuri,
Thank you very much, "via off" did the trick. It is probably a server
specific issue as you said.
Best Regards,
On Fri, Jun 24, 2016 at 6:29 PM, Rafael Akchurin <
rafael.akchu...@diladele.com> wrote:
> Hello Ozgur, Yuri,
>
>
>
> I also see this error. Actually it is even presen
Hello Ozgur, Yuri,
I also see this error. Actually it is even present on videos.yahoo.com if I am
not mistaken.
The reason for this is unclear for me (incorrect handling of “Via” header by
some of back office servers of Yahoo???)
I was able to fix it by setting “via off” in squid.conf. I am not
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hm. My opinion is the same - this is redirection loop. Just need to
localize it.
24.06.2016 20:23, Ozgur Batur пишет:
> Hi Yuri,
>
> Thank you. I put the #301 loop directives and restarted squid
unfortunately result is the same. Here is the acces
Hi Yuri,
Thank you. I put the #301 loop directives and restarted squid unfortunately
result is the same. Here is the access logs:
1466777191.791235 ::1 TCP_MISS/301 987 GET https://www.flickr.com/ -
HIER_DIRECT/188.125.93.100 text/html
1466777192.031237 ::1 TCP_MISS/301 987 GET https://ww
hi wen using ecap adapter
ecap_enable on
acl HTTP_STATUS_OK http_status 200
loadable_modules /usr/local/lib/ecap_adapter_gzip.so
ecap_service gzip_service respmod_precache ecap://www.vigos.com/ecap_gzip
bypass=off
adaptation_access gzip_service allow HTTP_STATUS_OK
wen the link has status 200 an
Try to do something like:
# 301 loop
acl text_mime rep_mime_type text/html text/plain
acl http301 http_status 301
store_miss deny text_mime http301
send_hit deny text_mime http301
24.06.2016 18:14, Ozgur Batur пишет:
I receive too many redirects(301 responses with same page URL) error
on br
I receive too many redirects(301 responses with same page URL) error
on browser when opening https://www.flickr.com via Squid 3.5 proxy
with SSL interception. If I connect to flickr website directly without
Squid error does not happen.
I tested it on two different systems one is Centos other is U
18 matches
Mail list logo
