Some segments-web payloads might be inaccurately empty
The segments-web.ligo.org payload page is showing that while some recent payloads (json and coalesced json) returned full payloads, some other formats returned empty payloads (ascii, tsv).
There may be 2 issues here:
-
Comparing an old query (pre-RL8, i.e., before 1 May 2024), like this one that returned no segments produced a valid JSON file with no known or active segments, and the same query produced an empty ASCII page. Newer empty ASCII pages (like this one), return a page that says
Not Found The requested URL was not found on this server.
. -
It looks like all non-json payloads are being returned empty, i.e.,
Not Found
, since the server upgrade (1 May 2024), even when the corresponding json payload contains segments. (Note that it might be that a valid ASCII payload exists, but whatever is producing theNot Found
issue might be preventing it from being served, thus this would be a symptom of the first issue, not a separate issue. Further investigation is needed to determine which is the case.)