Recently published a nonflash tease with a lot of xhamster videos in it. (https://milovana.com/webteases/showteas ... 3387&p=3#t)
As suggested in the forum (viewtopic.php?f=5&t=8416&p=108939), I just put the videos' urls in the tease text.
When viewing the tease, space is allocated for the frame, but most people can't see the video (some can) (viewtopic.php?f=2&t=18762).
Do I need to do something different, or is this feature broken?
Thanks!
Embed xhamster videos in nonflash tease
-
- Explorer
- Posts: 87
- Joined: Mon Dec 09, 2013 3:26 am
- Gender: Male
- Sexual Orientation: Straight
- I am a: Submissive
Re: Embed xhamster videos in nonflash tease
Oh, I think you've done everything right. It's just that xHamster doesn't support encrypted connections while Milovana doesn't support unencrypted connections (http vs https). And for example Internet Explorer, Chrome and Firefox don't currently allow unencrypted frames in encrypted pages (mixed active content) in their default configuration because it's "insecure". Either the user has to disable this protection temporarily or permanently, or you could use a different video platform (but as far as I can see none of them work). Asking xHamster to switch to https would probably be to no avail since it would break their http frames in turn.
https://developer.mozilla.org/en-US/doc ... ed_content
The gist of the security concerns is, implying you could trust the websites in the first place, that a bad guy in the middle could read or replace the unencrypted frame content on its way to the users browser and thereby gather information or hijack the whole browser tab. On the other hand decrypting or replacing encrypted content is not possible since bad guys usually don't have access to keys or trustworthy certificates.
Visiting the unencrypted website directly is just as insecure as having it embedded inside a encrypted page. But then it's the users choice.
Firefox:
Chrome:
Internet Explorer:
https://developer.mozilla.org/en-US/doc ... ed_content
The gist of the security concerns is, implying you could trust the websites in the first place, that a bad guy in the middle could read or replace the unencrypted frame content on its way to the users browser and thereby gather information or hijack the whole browser tab. On the other hand decrypting or replacing encrypted content is not possible since bad guys usually don't have access to keys or trustworthy certificates.
Visiting the unencrypted website directly is just as insecure as having it embedded inside a encrypted page. But then it's the users choice.
Firefox:
Chrome:
Internet Explorer:
Who is online
Users browsing this forum: No registered users and 25 guests