Lots of "BUG 3279: HTTP reply without Date:" after update to squid-5.0.0-20171117-r4d27d0a

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
5 messages Options
Reply | Threaded
Open this post in threaded view
|

Lots of "BUG 3279: HTTP reply without Date:" after update to squid-5.0.0-20171117-r4d27d0a

Ralf Hildebrandt
I was updating from squid-5.0.0-20171103-re3bf07f
to                  squid-5.0.0-20171117-rd816577 (and I was also testing squid-5.0.0-20171117-r4d27d0a)

today and immediately found lots of "BUG 3279: HTTP reply without
Date:" messages in my log (cache_dir had been cleared upon start,
meaning I'm starting with a clean slate!):

2017/11/22 11:16:02| BUG 3279: HTTP reply without Date:
2017/11/22 11:16:02| StoreEntry->key: 2CD6020000000000B515000000000000
2017/11/22 11:16:02| StoreEntry->next: 0x405f50e8
2017/11/22 11:16:02| StoreEntry->mem_obj: 0x35969af0
2017/11/22 11:16:02| StoreEntry->timestamp: 0
2017/11/22 11:16:02| StoreEntry->lastref: 1511345762
2017/11/22 11:16:02| StoreEntry->expires: 1511345762
2017/11/22 11:16:02| StoreEntry->lastModified_: -1
2017/11/22 11:16:02| StoreEntry->swap_file_sz: 0
2017/11/22 11:16:02| StoreEntry->refcount: 1
2017/11/22 11:16:02| StoreEntry->flags: REVALIDATE_ALWAYS,RELEASE_REQUEST,DISPATCHED,PRIVATE,VALIDATED
2017/11/22 11:16:02| StoreEntry->swap_dirn: -1
2017/11/22 11:16:02| StoreEntry->swap_filen: -1
2017/11/22 11:16:02| StoreEntry->lock_count: 3
2017/11/22 11:16:02| StoreEntry->mem_status: 0
2017/11/22 11:16:02| StoreEntry->ping_status: 2
2017/11/22 11:16:02| StoreEntry->store_status: 1
2017/11/22 11:16:02| StoreEntry->swap_status: 0
2017/11/22 11:16:03| BUG 3279: HTTP reply without Date:
2017/11/22 11:16:03| StoreEntry->key: 13D6020000000000B515000000000000
2017/11/22 11:16:03| StoreEntry->next: 0
2017/11/22 11:16:03| StoreEntry->mem_obj: 0x57a85d0
2017/11/22 11:16:03| StoreEntry->timestamp: 0
2017/11/22 11:16:03| StoreEntry->lastref: 1511345762
2017/11/22 11:16:03| StoreEntry->expires: 1511345763
2017/11/22 11:16:03| StoreEntry->lastModified_: -1
2017/11/22 11:16:03| StoreEntry->swap_file_sz: 0
2017/11/22 11:16:03| StoreEntry->refcount: 1
2017/11/22 11:16:03| StoreEntry->flags: RELEASE_REQUEST,DISPATCHED,PRIVATE,VALIDATED
2017/11/22 11:16:03| StoreEntry->swap_dirn: -1
2017/11/22 11:16:03| StoreEntry->swap_filen: -1
2017/11/22 11:16:03| StoreEntry->lock_count: 3
2017/11/22 11:16:03| StoreEntry->mem_status: 0
2017/11/22 11:16:03| StoreEntry->ping_status: 2
2017/11/22 11:16:03| StoreEntry->store_status: 1
2017/11/22 11:16:03| StoreEntry->swap_status: 0
2017/11/22 11:16:03| BUG 3279: HTTP reply without Date:
2017/11/22 11:16:03| StoreEntry->key: 6AD6020000000000B515000000000000
2017/11/22 11:16:03| StoreEntry->next: 0
2017/11/22 11:16:03| StoreEntry->mem_obj: 0x2fe3e2b0
2017/11/22 11:16:03| StoreEntry->timestamp: 0
2017/11/22 11:16:03| StoreEntry->lastref: 1511345763
2017/11/22 11:16:03| StoreEntry->expires: 1511345763
2017/11/22 11:16:03| StoreEntry->lastModified_: -1
2017/11/22 11:16:03| StoreEntry->swap_file_sz: 0
2017/11/22 11:16:03| StoreEntry->refcount: 1
2017/11/22 11:16:03| StoreEntry->flags: REVALIDATE_ALWAYS,RELEASE_REQUEST,DISPATCHED,PRIVATE,VALIDATED
2017/11/22 11:16:03| StoreEntry->swap_dirn: -1
2017/11/22 11:16:03| StoreEntry->swap_filen: -1
2017/11/22 11:16:03| StoreEntry->lock_count: 3
2017/11/22 11:16:03| StoreEntry->mem_status: 0
2017/11/22 11:16:03| StoreEntry->ping_status: 2
2017/11/22 11:16:03| StoreEntry->store_status: 1
2017/11/22 11:16:03| StoreEntry->swap_status: 0

is this a known bug with the recent snapshot?


--
Ralf Hildebrandt                   Charite Universitätsmedizin Berlin
[hidden email]        Campus Benjamin Franklin
https://www.charite.de             Hindenburgdamm 30, 12203 Berlin
Geschäftsbereich IT, Abt. Netzwerk fon: +49-30-450.570.155
_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|

Re: Lots of "BUG 3279: HTTP reply without Date:" after update to squid-5.0.0-20171117-r4d27d0a

joseph
after investigating  bug was exist but hidden all update ar correct
https://bugs.squid-cache.org/show_bug.cgi?id=3279
bug 3279  not yet fixed in v5
hint if they adapt the v3 patch will solve the problem :)



-----
**************************
***** Crash to the future  ****
**************************
--
Sent from: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
************************** ***** Crash to the future **** **************************
Reply | Threaded
Open this post in threaded view
|

Re: Lots of "BUG 3279: HTTP reply without Date:" after update to squid-5.0.0-20171117-r4d27d0a

Amos Jeffries
Administrator
In reply to this post by Ralf Hildebrandt
On 22/11/17 23:33, Ralf Hildebrandt wrote:
> I was updating from squid-5.0.0-20171103-re3bf07f
> to                  squid-5.0.0-20171117-rd816577 (and I was also testing squid-5.0.0-20171117-r4d27d0a)
>
> today and immediately found lots of "BUG 3279: HTTP reply without
> Date:" messages in my log (cache_dir had been cleared upon start,
> meaning I'm starting with a clean slate!):
>
> 2017/11/22 11:16:02| BUG 3279: HTTP reply without Date:
...
 >
> is this a known bug with the recent snapshot?
>

Yes, it still happens when a server delivers responses without a Date
header. Though IIRC it is mostly seen in the cases where an IMS/INM
conditional response is returning without a Date header (a message state
which is forbidden in HTTP).
  Taking a wild guess I suspect they are probably occuring when a client
revalidating its client-side cached content from one of the broken
servers. Or slightly less likely one of the early responses in cache_mem
right after the restart has the problem.


The patch joseph referred to synthesizes a fake Date header some time
far in the past. Thus forcing the content to become 'stale' in the
cache. That can either led to further refresh conditionals which
perpetuate the problem, or to purging the object from cache - thus
causing extra long fetch times for all traffic to that server.

Current Squid should only be logging that message at a relatively high
debug level (not important anymore) and synthesizing a Date header only
when the 2xx status is delivered to the client - the object cannot be
used for revalidation due to the missing header.


Amos
_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|

Re: Lots of "BUG 3279: HTTP reply without Date:" after update to squid-5.0.0-20171117-r4d27d0a

Amos Jeffries
Administrator
In reply to this post by joseph
On 23/11/17 01:25, joseph wrote:
> after investigating  bug was exist but hidden all update ar correct
> https://bugs.squid-cache.org/show_bug.cgi?id=3279
> bug 3279  not yet fixed in v5
> hint if they adapt the v3 patch will solve the problem :)
>
>

So according to the latest info you posted to that bug report a patch
which merely alters how logging displays a text string suddenly makes
inbound traffic to your proxy contain no Date headers.

Something is seriously wrong with your system.

Amos
_______________________________________________
squid-users mailing list
[hidden email]
http://lists.squid-cache.org/listinfo/squid-users
Reply | Threaded
Open this post in threaded view
|

Re: Lots of "BUG 3279: HTTP reply without Date:" after update to squid-5.0.0-20171117-r4d27d0a

joseph
This post was updated on .
Amos Jeffries wrote
> On 23/11/17 01:25, joseph wrote:
>> after investigating  bug was exist but hidden all update ar correct
>> https://bugs.squid-cache.org/show_bug.cgi?id=3279
>> bug 3279  not yet fixed in v5
>> hint if they adapt the v3 patch will solve the problem :)
>>
>>
>
>>>So according to the latest info you posted to that bug report a patch
>>>which merely alters how logging displays a text string suddenly makes
>>>inbound traffic to your proxy contain no Date headers.
 yes
>>>Something is seriously wrong with your system.
 not only me re read this post  the time i post in bug section i have my
cache.log  large enough to make me wonder
 and  more ppl i know using latest snap... got those date bug  header in
 log
> Amos
> _______________________________________________
> squid-users mailing list

> squid-users@.squid-cache

> http://lists.squid-cache.org/listinfo/squid-users





-----
**************************
***** Crash to the future  ****
**************************
--
Sent from: http://squid-web-proxy-cache.1019090.n4.nabble.com/Squid-Users-f1019091.html
_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
************************** ***** Crash to the future **** **************************