Hello Dear Amos: Thanks again , and i will try to bypass same traffic via firewall in according to your advisement . John Whether bypass the part TAG_NONE/400 4413 NONE error:invalid-request - HIER_NONE/- text/html at access.log *Amos Jeffries* squid3 at treenet.co.nz <mailto:squid-users%40lists.squid-cache.org?Subject=Re%3A%20%5Bsquid-users%5D%20Whether%20bypass%20the%20part%20TAG_NONE/400%204413%20NONE%0A%20error%3Ainvalid-request%20-%20HIER_NONE/-%20text/html%20at%20access.log&In-Reply-To=%3C56DBFEB8.9040904%40treenet.co.nz%3E> /Sun Mar 6 09:56:08 UTC 2016/ * Previous message: Whether bypass the part TAG_NONE/400 4413 NONE error:invalid-request - HIER_NONE/- text/html at access.log <http://lists.squid-cache.org/pipermail/squid-users/2016-March/009555.html> * Next message: Just a simple question about ACL <http://lists.squid-cache.org/pipermail/squid-users/2016-March/009557.html> * *Messages sorted by:* [ date ] <http://lists.squid-cache.org/pipermail/squid-users/2016-March/date.html#9560> [ thread ] <http://lists.squid-cache.org/pipermail/squid-users/2016-March/thread.html#9560> [ subject ] <http://lists.squid-cache.org/pipermail/squid-users/2016-March/subject.html#9560> [ author ] <http://lists.squid-cache.org/pipermail/squid-users/2016-March/author.html#9560> ------------------------------------------------------------------------ On 6/03/2016 11:09 a.m., johnzeng wrote: >/ />/ Hello Dear Sir />/ />/ i found more error info at access.log />/ />/ 192.168.0.16 TAG_NONE/400 4413 NONE error:invalid-request - HIER_NONE/- />/ text/html />/ />/ Whether we can skip or bypass the TAG_NONE/400 ? / Skip or bypass what exactly? Squid is an HTTP proxy. It is reporting that something that was mot efinitely not HTTP, or when treated as HTTP came out all mangled up. Got sent to the proxy. The input gets consumed while parsing. So it is likely already gone by the time bypass can happen in Squid. It *might* (very slim chance) be possible to bypass it at a firewall or routing level before it ever gets near Squid. But to do that you need a much clearer idea of what traffic it is that you are dealing with. >/ />/ if it wont't affect normal access , Whether we can skip the part at />/ access.log and too more same info at access.log . / A few odd ones will not affect anything. But if you are seeing these frequently enough to be annoying in the logs then it is affecting the bandwidth, CPU, RAM, and socket resources needed by legitimate traffic. >/ />/ i guess these error info is request or reponse from Mobile app . / It is *not* a request or respone. That is the problem. If it was Squid could handle it. If you can find out what it actually is. Then that should lead to a proper solution. Amos _______________________________________________ squid-users mailing list squid-users@xxxxxxxxxxxxxxxxxxxxx http://lists.squid-cache.org/listinfo/squid-users
