Sebastiaan has provided a workaround for this on the issue tracker and we're looking into getting it fixed in an upcoming release. So keep an eye on the issue:
Had this issue recently.
For me I was trying tho display a content that I created using the ContentService but I was just "saving" it, not "saving and publishing". One I published it the issue went away.
A potentially dangerous Request.Path value was detected from the client (:).
I'm trying to add a YouTube Url into the embed option in the grid section.
It retrieves the video, i can change the width and height of it, it appears in the grid editor, but at the frontend i get a server error.
The url i'm using is: https://www.youtube.com/watch?v=47GphaQjxo&feature=emblogo
or
https://www.youtube.com/watch?v=47GphaQj_xo
Both of these give me the server error.
Even if i remove the https://, which contains the ":" it still doesn't work.
Who can help me out?
It also goes wrong with a vimeo url.
And still haven't found a solution for this problem.
Please try with the below url
https://youtu.be/47GphaQj_xo
I did, same error unfortunately
Are you able to modify your web.config in the root of the application? Try adding this in the system.web section:
Already did that. No positive result
I also have this problem, haven't found a solution yet unfortunately
I'm also getting this issue. I've reported as a bug here as it seems to have only started recently - my existing embedded videos display ok.
As i'm starting with a new project i've got no existing embedded videos in the site.
What i do know is that it works perfectly in the RTE outside the Grid. But that isn't the solution. I need it to work inside the Grid.
If you add the RTE editor to your grid and embed the video manually in the source of the RTE editor that will work.
That will work indeed, but it's not "idiot" proof.
Got an answer from Umbraco on Twitter:
Workaround on GitHub
Had this issue recently. For me I was trying tho display a content that I created using the ContentService but I was just "saving" it, not "saving and publishing". One I published it the issue went away.
is working on a reply...