[squid-users] TCP_MISS/429

[M***@berge-meer.de]

Hi everyone,

this is the first time i use a mailinglist, so i hope i don't mess things
up.

I encountered a very strange TPC_MISS/429 in my squid access.log.
1440405573.871 285 10.2.0.5 TCP_MISS/429 255 GET http://crushftp.com/
Preism HIER_DIRECT/104.236.78.254 -

I've searched the web, but nothing fount yet. The Webpage is blank. When i
try from home, everything works fine.
http://wiki.squid-cache.org/SquidFaq/SquidLogs#access.log does not list
the status code.

I'm not sure if this error is maybe: "Too Many Requests. The user has sent
too many requests in a given amount of time"
If it is, i dunno why. I got this error right when i tried to open the
webpage for the very first time.
Hope someone can help me.

best regards
Markus

___________________________________________________________________________

Markus Preis


Berge & Meer Touristik GmbH
Andréestrasse 27
56578 Rengsdorf

Tel: [phone]

Fax: [phone]
Mailto:***@berge-meer.de
http://www.berge-meer.de

Melden Sie sich unter https://www.berge-meer.de/newsletter?f=1762 fÃŒr unseren Newsletter an und erhalten Sie jede Woche kostenlos die aktuellsten Reiseangebote

Berge & Meer Touristik GmbH
Handelsregistergericht: Montabaur/HRB 13067
Sitz: Rengsdorf
GeschÀftsfÌhrer: Thomas Klein (Vorsitzender), Tim Dunker, Marcel Mayer

Vertraulichkeitshinweis:
Diese E-Mail enthaelt vertrauliche und/oder rechtlich geschuetzte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtuemlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail ist nicht gestattet.

Confidential Note:
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail.
Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.

[Amos Jeffries]

Post by M***@berge-meer.de
Hi everyone,
this is the first time i use a mailinglist, so i hope i don't mess things
up.

No problem. Welcome.

Post by M***@berge-meer.de
I encountered a very strange TPC_MISS/429 in my squid access.log.
1440405573.871 285 10.2.0.5 TCP_MISS/429 255 GET http://crushftp.com/
Preism HIER_DIRECT/104.236.78.254 -
I've searched the web, but nothing fount yet. The Webpage is blank. When i
try from home, everything works fine.
http://wiki.squid-cache.org/SquidFaq/SquidLogs#access.log does not list
the status code.

see <http://tools.ietf.org/html/rfc6585#section-4> for what it means.

Squid does not generate that code itself. Although it is possible for an
admin to use "deny_info 429:ERR_BLANK someAcl" and have setup a custom
rate-limiting ACL helper.

In this case I think its just the normal traffic event with the origin
server 104.236.78.254 generating it.

Amos

[T3h vICE]

Thank you Amos for your thoughts.

I've tried some stuff to filter the error.
When i'm on my squidsever i can wget http://crushftp/index.html .
Trying to download the index.html on my Windowsclient gives me 429-Error
instead.
Has this maybe something to do with proxy transparency?



--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-MISS-429-tp4672839p4672856.html
Sent from the Squid - Users mailing list archive at Nabble.com.

[Amos Jeffries]

Post by T3h vICE
Thank you Amos for your thoughts.
I've tried some stuff to filter the error.
When i'm on my squidsever i can wget http://crushftp/index.html .
Trying to download the index.html on my Windowsclient gives me 429-Error
instead.
Has this maybe something to do with proxy transparency?

Might be. Might not be.

Squid is always properly transparent (in the HTTP meaning) by default.
If the TCP and IP and anonymity definitions of "transparent" are needed
or configured that is something only the admin of the proxy knows and
can change.


Might be that you are not the only user visiting that site through that
proxy, or one its traffic goes through further upstream.

Might be an old server with custom status code predating the specifications.

Might be a lot of other things. Only the admin of the server generating
it actually knows why and when the code is used.

Keep digging. Good luck.
Amos

[T3h vICE]

I turned
*forwarded_for on*
and deleted
*visible_hostname*
That did the job.

Thank you for your advise.
Maybe this helps someone someday, when facing the same error.



--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/TCP-MISS-429-tp4672839p4673054.html
Sent from the Squid - Users mailing list archive at Nabble.com.