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

Malformed URI error for adTagUrl when evaluating video tags that include umlauts #4057

Open
linkurzweg opened this issue Aug 13, 2019 · 11 comments

Comments

@linkurzweg
Copy link

I am using the mediaProxy to update the ad tag url on entry change (see #4043). For example the video tags with {mediaProxy.entry.tags}. This works fine as long as there are no umlauts (ä,ö,ü...) in the tags.

When the video has tags that include umlauts, this will cause the player to not play the video, it loads indefinitely. Also the ad server returns an URI malformed error in the console:
ima3.js?_=1565696493160:40 Uncaught URIError: URI malformed at decodeURIComponent (<anonymous>) at Jc (ima3.js?_=1565696493160:40) at ima3.js?_=1565696493160:393 at Object.Sc (ima3.js?_=1565696493160:387) at Bu (ima3.js?_=1565696493160:388) at Cu (ima3.js?_=1565696493160:390) at Eu.k.Ef (ima3.js?_=1565696493160:393) at mw.DoubleClick.requestAds (load.php?debug=false&lang=en&modules=...)

It looks like the player is not correctly encoding umlauts when evaluating the tags?
Also I think the video should not stop working, even if there is a problem with the ad tag url.

@OrenMe maybe you could take a look at this? Thank you!

@kaltura-hooks
Copy link

Hi @linkurzweg,

Thank for you reporting an issue and helping improve Kaltura!

To get the fastest response time, and help the maintainers review and test your reported issues or suggestions, please ensure that your issue includes the following (please comment with more info if you have not included all this info in your original issue):

  • Is the issue you're experiencing consistent and across platforms? or does it only happens on certain conditions?
    please provide as much details as possible.
  • Which Kaltura deployment you're using: Kaltura SaaS, or self-hosted?
    If self hosted, are you using the RPM or deb install?
  • Packages installed.
    When using RPM, paste the output for:
	# rpm -qa \"kaltura*\"
For deb based systems:
	# dpkg -l \"kaltura-*\"
  • If running a self hosted ENV - provide the MySQL server version used
  • If running a self hosted ENV - is this a single all in 1 server or a cluster?
  • If running a self hosted ENV, while making the problematic request, run:
	# tail -f /opt/kaltura/log/*.log /opt/kaltura/log/batch/*.log | grep -A 1 -B 1 --color \"ERR:\|PHP\|trace\|CRIT\|\[error\]\"

and paste the output.

  • When relevant, provide any screenshots or screen recordings showing the issue you're experiencing.

For general troubleshooting see:
https://github.com/kaltura/platform-install-packages/blob/Jupiter-10.13.0/doc/kaltura-packages-faq.md#troubleshooting-help

If you only have a general question rather than a bug report, please close this issue and post at:
http://forum.kaltura.org

Thank you in advance,

@OrenMe
Copy link
Contributor

OrenMe commented Aug 13, 2019

hi @linkurzweg the URI should contain valid characters and unfortunately we don't have a way to escape this via the evaluate tokens feature.

@linkurzweg
Copy link
Author

@OrenMe thanks for the quick reply! I didn't know umlauts are considered invalid characters, since urls with umlauts do exist. I guess there is no way to disallow the entering of invalid characters in the Kaltura Console? Because that's gonna be a problem with all the different people adding content for our platform.

@OrenMe
Copy link
Contributor

OrenMe commented Aug 13, 2019

I'm not sure this is the issue :-)
Do u have a test link?

@linkurzweg
Copy link
Author

linkurzweg commented Aug 13, 2019

I do have a test link, however I can't post that here. Can I contact you personally? Email?
Too bad there's no private messaging in GitHub anymore 🙄

@OrenMe
Copy link
Contributor

OrenMe commented Aug 13, 2019

please send to [email protected]

@linkurzweg
Copy link
Author

Thanks! I will right now :)

@OrenMe
Copy link
Contributor

OrenMe commented Aug 13, 2019

@linkurzweg I think this might be an issue with how the player escape cust_params.
Are you a platform user? if so can you please file a support request?

@linkurzweg
Copy link
Author

@OrenMe sorry, I am not... So how do we continue with this?

@OrenMe
Copy link
Contributor

OrenMe commented Aug 13, 2019

@linkurzweg I will open an issue in our internal bug tracker, but I do not have a due date for this yet.

@linkurzweg
Copy link
Author

@OrenMe ok, thank you! I understand. Can you get back to me once this will be fixed (whenever that might be)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

3 participants