[squid-users] TCP_MISS/403 353 HEAD text/plain Error help !!
snakeeyes
ahmed.zaeem at netstream.ps
Sun Jun 7 07:40:41 UTC 2015
Hi Amos thank you so much
Again , this App IS REMOTE and as a black box .
It works 100 % on other proxies but I need to let it work on my own proxy.
Now what I did is :
I added 2 directives to my squid.conf :
strip_query_terms off
debug_options 11,2 28,3
then restarted squid and monitored the logs .
again I have 2 files monitored when it worked and when it failed.
But the strange that the problem is it work on some youtube vidoes and don’t work on the others
those files were just as an example :
file 1 didn’t work and give error 403 ===> https://www.youtube.com/watch?v=MYSVMgRr6pw
and other file worked ===>
https://www.youtube.com/watch?v=p0g9_osImd0
now I will test the app with those links , note that that 1sst line will fail and the 2nd Link will success.
I had graped the log files andf attached them because they are big
Name for failed file is =>debug_failed.txt
Name for succeded file ==>debug_worked.txt
Thanks a lot
cheers
-----Original Message-----
From: squid-users [mailto:squid-users-bounces at lists.squid-cache.org] On Behalf Of Amos Jeffries
Sent: Friday, June 5, 2015 4:05 PM
To: squid-users at lists.squid-cache.org
Subject: Re: [squid-users] TCP_MISS/403 353 HEAD text/plain Error help !!
On 6/06/2015 6:47 a.m., snakeeyes wrote:
> Hello All
>
> I want to ask how could I get out the log
>
> TCP_MISS/403 353 HEAD text/plain Error ?????
>
> I have many logs in cach.log about that and I want to figure out this
> issue !
>
> Aby help ?
>
The posts you made earlier (including the private one) do not have sufficient content to be able to help you.
Firstly, we definitely need to see the full URLs in access.log. So your squid.conf needs to contain "strip_query_terms off" to see what stage the YT request sequence is at.
For tracking down why the status is being given you will want "debug_options 11,2 28,3" to log in cache.og the HTTP request/reply headers and ACL proccessing decisions.
If you can run with debugs set to ALL,5 to get a more full trace that would be excellent. But it will definitely produce a lot of data, so thats optional. The above mentioned two sections should be sufficient to identify teh next steps forward, and will produce a lot of info anyway.
Amos
_______________________________________________
squid-users mailing list
squid-users at lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: debug_worked.txt
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20150607/27af9ed9/attachment-0002.txt>
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: debug_fail.txt
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20150607/27af9ed9/attachment-0003.txt>
More information about the squid-users
mailing list