Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

A standard for URL fragment #678

crocket opened this issue Nov 4, 2019 · 2 comments


Copy link

@crocket crocket commented Nov 4, 2019

Currently, there is no agreed standard for multiple parameters in URL fragment.
Cantata has stored stream name in URL fragment for years. MPD recently started storing charset in URL fragment. There needs to be an agreement between MPD and MPD clients with regard to URL fragment format.

I suggest


It's an ampersand-separated list of key-value pairs. Values are URL-encoded.
The separator between key and value can be = or some other character that doesn't conflict with URL encoding.

Cantata developer agrees with using ampersand. He may have opinions on the separator between key and value.


This comment has been minimized.

Copy link

@MaxKellermann MaxKellermann commented Nov 4, 2019

There is no standard because right now, MPD supports only the "charset" parameter.
But your suggestion makes sense, and there are already other programs who are doing it that way. I'd agree to add this definition to the MPD documentation.


This comment has been minimized.

Copy link

@crocket crocket commented Nov 4, 2019

Cantata developer implemented my suggestion. Cantata adds StreamName parameter to URL fragment when I play a stream from a playlist.

MPD seems to already support this amersand-separated list of key-value pairs.

I think MPD clients would benefit a lot if you added this URL fragment definition to MPD documentation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
None yet
2 participants
You can’t perform that action at this time.