BAD_HTTP_STATUS with status 304

[martinstark]

Have you read the Tutorials?
yes

Have you read the FAQ and checked for duplicate open issues?
yes

If the question is related to FairPlay, have you read the tutorial?

n/a

What version of Shaka Player are you using?
4.12.2

What browser and OS are you using?
n/a

Please ask your question

Looking in our KPI tracking, I found a few BAD_HTTP_STATUS errors with status 304:

{
    severity: 2,
    category: 1,
    code: 1001,
    data: [
      "<snip>/hls/bbf75050-ac3b-11ef-8c9a-1f00a50fe182_20876973-audio=128000-496.m4s",
      304,
      "",
      {
        "cache-control": "max-age=29831259, s-maxage=31536000",
        // snip
      },
      1,
      "<snip>/hls/bbf75050-ac3b-11ef-8c9a-1f00a50fe182_20876973-audio=128000-496.m4s",
    ],
    handled: false,
    message: "Shaka Error 1001",
    stack:
      "Error: Shaka Error 1001 <snip>",
  },

I'm not entirely sure if this is a bug, what might cause Shaka to throw when hitting browser cache for a segment?

[avelad]

Maybe https://github.com/shaka-project/shaka-player/blob/main/lib/net/http_plugin_utils.js#L35?

[martinstark]

That seems like a bug, in case the browser has the segment in cache already 🤔

[avelad]

We'll let @joeyparrish decide, he knows this part best.