Open bynt opened 5 years ago
Thank you for creating the issue! One of our team members will get back to you shortly with additional information.
UPDATE last import of outdated version of advisory 4053440 was on February, 20th 23:03 UTC.
looking good since then. I'll keep You updated.
Describe the bug We check the Security Advisory feed
once every 3600s for updates. Since February 4th, ~2130 UTC we occasionally crawl outdated versions of
in this way. Most of the time we get V3.0 of the advisory, sometimes we receive an older version.
To Reproduce Steps to reproduce the behavior:
Expected behavior always get the latest version of each advisory
Screenshots n/a
Desktop n/a, only source code is processed
Additional context In the example given, the source code of the latest version hints at the use of markdown language for the content of the provided advisories, e. g. 'sourcefile', 'sourcestartline' and 'sourceendline' in
<h1 id="microsoft-security-advisory-4092731" sourcefile="SecurityAdvisories/2018/4092731.md" sourcestartlinenumber="1" sourceendlinenumber="1">Microsoft Security Advisory 4092731</h1>
According to tech team, these markdown features are not present in the source code of the outdated advisory we occasionally find at the same URL. Maybe there is something like loadbalancing involved and we occasionally receive
from a server that does not know of markdown or didn't receive the (alleged) February 4th security advisory markdown update?
Edit The issue may also be related to Akamai's CDN services.