Did webdav url format changed in Web 8.5? When I am calling folder.LocationInfo.WebDavUrl API the below output it is returning


When I tried with 2013 Core service url it used to return


2 Answers 2


I don't think anything specific to Webbdav url is changed in Web 8.5. Probably underlying framework is handling url encoding a bit differently. If you do Url decoding of both Webbdav paths, you would see two identical strings.

  • I also recall, during a recent upgrade, that we had some questions on encoding in other areas so I agree that it looks like the underlying framework was changed (perhaps to catch additional characters). Commented Jun 11, 2019 at 7:12
  • 2
    That is correct, behavior of Uri.EscapeDataString(urlString) method was changed in .NET Framework 4.6.2. See more details in section ".NET method Uri.EscapeDataString(urlString) has changed behavior" in the release notes: docs.sdl.com/LiveContent/content/en-US/SDL%20Tridion%20Sites-v1/…
    – AntonM
    Commented Jun 11, 2019 at 12:49


I see these encoded in my test system also. From what I understand of WebDAV, encoding these shouldn't cause an issue. I presume both values function the same?

UPDATE: I understand that parenthesis' are classified as sub-delimiters (W3C) so I wonder if they need to be treated differently as part of a URL as with being part of a set of URL Parameters.

Point taken on the pain of doing a direct comparison of file content post upgrade during a file comparison - I guess you'd have to change you checker to account for specific (non-impacting) encoding differences.

  • Agree with you Shahid, Those will fail if we try to do string compare, same issue i have faced while migrating custom page from 2013 SP1, Thought it may be helpful so posted question. Commented Jun 10, 2019 at 18:29

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.