[squid-users] some error using squid-3.0 stable 12

Dear all,

I am presently using squid-3.0 Stable12 and it seems it is working smoothly, however I am seeing some messages on the cache.log which is similar to the logs I have seen from the previous version. I am worried that in due time my squid squid will respond poorly to the request until it crash.

I am getting messages as: WARNING: HTTP header contains NULL characters {Accept: */*
Content-Type: application/x-www-form-urlencoded}, http.cc(561) HttpStateData::cacheableReply: unexpected http status code 0 and http.cc(561) HttpStateData::cacheableReply: unexpected http status code 554.

Can anybody interpret the above messages? Is it a serious problem? If it is, can you please help ma how to fix it?

Below are the messages from cache.log
  

2009/01/28 08:56:11| WARNING: HTTP header contains NULL characters {Accept: */*
Content-Type: application/x-www-form-urlencoded}
2009/01/28 08:56:17| WARNING: HTTP header contains NULL characters {Accept: */*
Content-Type: application/x-www-form-urlencoded}
2009/01/28 08:56:17| WARNING: HTTP header contains NULL characters {Accept: */*
Content-Type: application/x-www-form-urlencoded}
2009/01/28 08:56:26| WARNING: HTTP header contains NULL characters {Accept: */*
Content-Type: application/x-www-form-urlencoded}
2009/01/28 08:56:26| WARNING: HTTP header contains NULL characters {Accept: */*
Content-Type: application/x-www-form-urlencoded}
2009/01/28 08:59:45| WARNING: HTTP header contains NULL characters {Accept: */*
Content-Type: application/x-www-form-urlencoded}
2009/01/28 08:59:45| WARNING: HTTP header contains NULL characters {Accept: */*
Content-Type: application/x-www-form-urlencoded}
2009/01/28 09:00:07| WARNING: HTTP header contains NULL characters {Accept: */*
Content-Type: application/x-www-form-urlencoded}
2009/01/28 09:00:07| WARNING: HTTP header contains NULL characters {Accept: */*
Content-Type: application/x-www-form-urlencoded}

2009/01/28 09:10:06| ctx: enter level 0: 'http://msgr.updates.yahoo.com/vitality_proxy/V1/getEvents?max=10&since=1214595458&includeStatus=true&alias=libethharoun&fmt=2.0&intl=us&os=win&ver=9.0.0.2034&buddies=(babeezen,dpotter144,ellynverula,emely_abilar,feyroda,g_unit_thug78,hananrubio,hapakan,helen_1083gcam,joy_s_namoc,lamdagan%40sbcglobal.net,leo_jnd132,llpll26,loulamdagan,manildz_143,maryltejada,minmin3759,ram_grace68,reign_ron_26ci,rhiza_m,ronnie_navea,sintarose56,stalag40,v_duroy,vfloresgueco,wiengar,yveschristianv,zkglim)'
2009/01/28 09:10:06| http.cc(561) HttpStateData::cacheableReply: unexpected http status code 0
2009/01/28 09:10:11| ctx: exit level 0
2009/01/28 09:10:11| ctx: enter level 0: 'http://msgr.updates.yahoo.com/vitality_proxy/V1/getEvents?max=10&alias=jayanthianand4&fmt=2.0&intl=us&os=win&ver=9.0.0.2018&buddies=(anandshashank%40rocketmail.com,balji_19,chinna_suyambunathan,citnaren,jaanand4,jayaanand2001,ramyajayapal,sareswathy,sbgpcmanand,sbgshashank,suresh2903)'
2009/01/28 09:10:11| http.cc(561) HttpStateData::cacheableReply: unexpected http status code 554

Thank you very much and best regards,
Received on Wed Jan 28 2009 - 06:12:49 MST