>Can you test if the details at bug 4253:
>
>http://bugs.squid-cache.org/show_bug.cgi?id=4253#c13
>
>Helps you to resolve the issue?
>
>Eliezer
The above bug is not related to the issue.
The issue is actually on origin servers side. Details can be found
here:
From: squid-users [mailto:squid-users-boun...@lists.squid-cache.org] On Behalf
Of Ozgur Batur
Sent: Monday, June 27, 2016 6:02 PM
To: Amos Jeffries
Cc: squid-users@lists.squid-cache.org
Subject: Re: [squid-users] flickr.com redirect error
Browser i used to test runs on same machine with squ
Browser i used to test runs on same machine with squid, i changed it to
explicit mode(no intercept - I set proxy ip in browser) during my attempts
for ssl interception. Sorry I forgot to mention that in my last post of
logs. So xff localhost is normal I guess. Here is the request log with
port
On 27/06/2016 11:01 p.m., Ozgur Batur wrote:
> Yes that is much easier, thank you.
>
> Rafaels line is response header, I received the same. Here is the related
> cachelog:
>
What is the content of the line above this one. With the IP:port details ?
> 2016/06/27 13:52:49.194 kid1| 11,2|
Yes that is much easier, thank you.
Rafaels line is response header, I received the same. Here is the related
cachelog:
2016/06/27 13:52:49.194 kid1| 11,2| http.cc(2235) sendRequest: HTTP Server
REQUEST:
GET / HTTP/1.1
Accept:
On 27/06/2016 9:04 p.m., Ozgur Batur wrote:
> Hello Amos,
>
> This is the via header sent by my local proxy as part of the request.
> *Via: 1.1 ubuntuozgen (squid/3.5.19)*
>
> It is not fqdn but ubuntu concatanated with a Turkish name so it is highly
> unlikely that yahoo have such named reverse
Hello Amos,
This is the via header sent by my local proxy as part of the request.
*Via: 1.1 ubuntuozgen (squid/3.5.19)*
It is not fqdn but ubuntu concatanated with a Turkish name so it is highly
unlikely that yahoo have such named reverse proxy. I could not decrypt the
squid <--> flicker traffic
On 25/06/2016 6:14 p.m., Rafael Akchurin wrote:
> 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
quid-users] flickr.com redirect error
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?
Ther
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
-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,
*Sent:* Friday, June 24, 2016 4:23 PM
> *To:* Yuri <yvoi...@gmail.com>
> *Cc:* squid-users@lists.squid-cache.org
> *Subject:* Re: [squid-users] flickr.com redirect error
>
>
>
> Hi Yuri,
>
>
>
> Thank you. I put the #301 loop directives and restarted squi
Re: [squid-users] flickr.com redirect error
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<http://188.12
-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
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
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
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
18 matches
Mail list logo
