You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The URL Standard describes how to combine a string with a relative path with a base URL to produce a valid absolute URL.
This feature request is: given an absolute URL and a base URL, produce a string with a relative path that when joined to the base URL, would produce the original absolute URL.
This is similar to file system path operations like Go's Rel and Python's relpath.
Practical application: some HLS video players expect relative paths, despite the HLS spec allowing for absolute paths. I want to produce correct relative paths given the relevant absolute ones.
What is the feature you are proposing to solve the problem?
What is the problem this feature will solve?
The URL Standard describes how to combine a string with a relative path with a base URL to produce a valid absolute URL.
This feature request is: given an absolute URL and a base URL, produce a string with a relative path that when joined to the base URL, would produce the original absolute URL.
This is similar to file system path operations like Go's Rel and Python's relpath.
Practical application: some HLS video players expect relative paths, despite the HLS spec allowing for absolute paths. I want to produce correct relative paths given the relevant absolute ones.
What is the feature you are proposing to solve the problem?
Some function like:
Example:
https://example.org:8080/origin/multivariant/playlist.m3u8
https://example.org:8080/origin/media/1080p.m3u8
../media/1080p.m3u8
What alternatives have you considered?
Using the file system tools.
The text was updated successfully, but these errors were encountered: