Path to content mismatch (more than one dot in domain name creates mismatch, because extra slash is added by the system)!

Bugs
1

Product

Encoding - VOD

Question

After input of:

https://filmbookingstorage.blob.core.windows.net/streamingassets/017f6bad-e4a7-458e-efa0-08dcaae2f648.mp4

I get:
The provided Input URL cannot be reached, please check ‘https://filmbookingstorage.blob.core.windows.net//streamingassets/017f6bad-e4a7-458e-efa0-08dcaae2f648.mp4’ for correctness

After windows.net there is // instead of / !!!

All our encodings now get errors : Download of input file failed. File not found on storage.

This happens from Azure storage.

One / too many. Has to be removed.

I created a ticket, but nobody is responding. This is critical.

Just try to create an encoding manually to reproduce.

2

Hi Peter,

Sorry to hear you’re having an issue with this.
How are you defining the input path string? is there an extra forward slash in the base_url of your config? (e.g. base_url = "https://filmbookingstorage.blob.core.windows.net/" )

If you take a look at one of our dotNet examples, you’ll see that we use Path.join() to build absolute paths - bitmovin-api-sdk-examples/dotnet/Bitmovin.Api.Sdk.Examples/FixedBitrateLadder.cs at fa64298d59bbdcc685fbc959da11ed00cfbc0f9d · bitmovin/bitmovin-api-sdk-examples · GitHub

3

Nothing is changed since a while and suddenly there is this issue. If you go to the manual creation of an VOD encoding and input:

https://filmbookingstorage.blob.core.windows.net/streamingassets/017f6bad-e4a7-458e-efa0-08dcaae2f648.mp4

you get an error. There are no double slaches here. But the error says there is!

4

I see, Peter. You’re using the dashboard encoding creation, not the API?

5

The API and the dashboard do the same thing.
Since last night.

6

Were you able to reproduce?

7

Hi Neil,

I really hope somebody can take a look at this. I do attach an image here. In the API the same thing is happening:

Schermafbeelding 2024-07-23 180145
Schermafbeelding 2024-07-23 1801453840×2064 435 KB

8

SDK 1.200 does not resolve the issue.

9

One more finding: this happens when there are more than one dots in the domain name:

https://subdomain.domain.com/file.mp4 translates into https://subdomain.domain.com//file.mp4

Schermafbeelding 2024-07-24 094213
Schermafbeelding 2024-07-24 0942133840×2064 391 KB

10

Thanks a lot, Peter. I’ve reported this to Engineering. I’ll update here once I get some feedback.

11

Hi Neil,

Thank you. I hope they can do something quickly.
Peter

12

Hi @peter.vanvogelpoel
Happy to let you know that a fix was just pushed for the dashboard. Can you please give it a quick try?

13

Dashboard seems to go well now. Through the API it still seems a problem.

14

Peter, I’ll message you so you don’t have to share any config publicly.