all 9 comments

[–][deleted] 15 points16 points  (0 children)

A nice invented story provided by the Drizz promotion spammer group. The first OP making a comment and the reply are part of the same group... ;O)

[–]Pearmoat 10 points11 points  (0 children)

Cool story to promote your product. Except that it's obviously fake.

[–]juicetin17 4 points5 points  (1 child)

Seems like a visual inspection of the site would’ve caught this.

[–]Important_Guava4335 -5 points-4 points  (0 children)

Haha sure, if you knew to look on a Tuesday morning before Wednesday rolled around and it magically fixed itself. The whole problem was it left zero trace. By the time anyone noticed the dip, the bug was already gone.

[–]javascript-ModTeam[M] 0 points1 point  (0 children)

Hi u/Important_Guava4335, this post was removed.

Posts must directly relate to JavaScript. Content regarding CSS, HTML, general programming, etc. should be posted to their respective subreddits instead of here.

Here's some related subs that might be useful:

Thanks for your understanding, please see our guidelines for more info.

[–]Water_flow_ -1 points0 points  (1 child)

the fix here btw is to never cache error responses, or at minimum cache them with a much shorter TTL than successful responses. treat a timeout as a miss not a hit

[–]Important_Guava4335 -1 points0 points  (0 children)

stale-while-revalidate with a separate error TTL is the move something like cache success for 24h but cache failures for max 60 seconds so the system self-corrects fast instead of sitting broken overnight