When did the unread counter poof?
-
well cloudflare or maybe some changes to nginx would make cloudflare act better.
-
@JaredBusch said in When did the unread counter poof?:
well cloudflare or maybe some changes to nginx would make cloudflare act better.
If you think of something to try on the nGinx side, let me know.
-
Wonder if this change in behavior is related to their recent incident?
-
@Danp said in When did the unread counter poof?:
Wonder if this change in behavior is related to their recent incident?
I was considering the same, but that was last Friday, and the changes to CloudFlare were made last weekend, I'm pretty sure (but not 100% positive) I had the counter on Monday.
-
@Danp said in When did the unread counter poof?:
Wonder if this change in behavior is related to their recent incident?
Not likely as it "working" was a new thing, too.
-
@Dashrender I thought that the counter reappearing occurred at approx the same time that Cloudflare identified the issue.
-
@Danp said in When did the unread counter poof?:
@Dashrender I thought that the counter reappearing occurred at approx the same time that Cloudflare identified the issue.
Before.
-
This thread indicates that it was found to be working 7 days ago... That would be Last Thursday at the latest. The CF problem was found late Friday afternoon/evening.
-
@Dashrender Actually, the problem was found earlier than that. This blog post is from last Thursday.
-
@scottalanmiller said in When did the unread counter poof?:
@JaredBusch said in When did the unread counter poof?:
well cloudflare or maybe some changes to nginx would make cloudflare act better.
If you think of something to try on the nGinx side, let me know.
The blog post mentions three features that they turned off whenever they initially addressed the issue with the parser bug. You could try turning these off one by one to see if that identifies the source of the issue.
-
@Danp said in When did the unread counter poof?:
@Dashrender Actually, the problem was found earlier than that. This blog post is from last Thursday.
OK looks like the actual incident took place on Feb 17, definitely not the understanding I got from listening to Security Now. They keep saying "Last Friday" as in Feb 24.
Thanks for the correction Dan.
So it looks like it was fixed for a short while after the incident.
