From a92a2710aac1e890b60ec68274365568640b9694 Mon Sep 17 00:00:00 2001 From: Michael Chisholm Date: Sat, 12 Mar 2022 21:00:27 +1100 Subject: [PATCH] Fix link to ContentDirectory spec (#21985) --- source/_integrations/dlna_dms.markdown | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/source/_integrations/dlna_dms.markdown b/source/_integrations/dlna_dms.markdown index 9dd39923b2b..abd3b32c0ac 100644 --- a/source/_integrations/dlna_dms.markdown +++ b/source/_integrations/dlna_dms.markdown @@ -31,7 +31,7 @@ The `` can have one of three forms: - `path/to/file` or `/path/to/file`: Slash-separated path through the Content Directory. This must refer to a unique media item. - `:ObjectID`: Colon followed by a server-assigned ID for an object. -- `?query`: Question mark followed by a query string to search for, see [DLNA ContentDirectory SearchCriteria](http://www.upnp.org/specs/av/UPnP-av-ContentDirectory-v1-Service.pdf) for the syntax. The first result found will be used. +- `?query`: Question mark followed by a query string to search for, see [DLNA ContentDirectory SearchCriteria](https://openconnectivity.org/wp-content/uploads/2015/11/UPnP-av-ContentDirectory-v4-Service.pdf) (part 5.3.16 "A_ARG_TYPE_SearchCriteria" on page 65 and part D.5 "Searching" on page 269) for the syntax. The first result found will be used. URIs generated while browsing will look like the Object ID form above. However, all three forms will work with the [media_player.play_media](/integrations/media_player/#service-media_playerplay_media) service.