Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Error 405 + Nginx

See original GitHub issue

Have you read the FAQ and checked for duplicate open issues? tried to look around didn’t find smth useful

What version of Shaka Player are you using? latest

Please ask your question why shaka player loads this m3u8 successfully

https://us.akami.dopemovie.cdn.nightproxy.com/test1/test1.m3u8

but fails with this

https://us.akami.dopemovie.cdn.nightproxy.com/test2/aac45a27-4bf5-4c51-b34c-cef25afa7cf3/_apis/git/repositories/0a9a750f-d64c-4775-9a99-7c213c0f40fa/items?path=/test1.m3u8


Request URL: https://us.akami.dopemovie.cdn.nightproxy.com/test2/aac45a27-4bf5-4c51-b34c-cef25afa7cf3/_apis/git/repositories/0a9a750f-d64c-4775-9a99-7c213c0f40fa/items?path=/test1.m3u8
Request Method: HEAD
Status Code: 405 
Remote Address: 94.245.93.91:443
Referrer Policy: no-referrer-when-downgrade

core.js:6210 ERROR Error: Uncaught (in promise): shaka.util.Error {
  "severity": 2,
  "category": 1,
  "code": 1001,
  "data": [
    "https://us.akami.dopemovie.cdn.nightproxy.com/test2/aac45a27-4bf5-4c51-b34c-cef25afa7cf3/_apis/git/repositories/0a9a750f-d64c-4775-9a99-7c213c0f40fa/items?path=/test1.m3u8",
    405,
    "",
    {
      "cache-control": "no-cache, no-store, must-revalidate",
      "content-length": "93",
      "content-type": "application/json; charset=utf-8",
      "expires": "-1",
      "pragma": "no-cache"
    },
    0
  ],
  "handled": false
}

i mean is the same test1.m3u8 file only url is longer, what’s the reason?!

Issue Analytics

State:
Created 3 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

TheModMakercommented, Jun 3, 2020

In the second URL, the .m3u8 at the end is part of a query parameters. They are just extra data to pass along with the request and do not affect the path being queried. The file path being queried is called items, you are just passing some extra data that happens to also have a file extension. But we have no way of knowing the query parameters are paths, they could be anything.

0reactions

therawcommented, Jun 3, 2020

@TheModMaker thanks for explanation