Could someone explain or help me understand why this HTTPS video link does not play on iPad and iPhone's web browser?
However, this HTTP link does play on iPad and iPhone's web browser.
Both are pointing to the same video file on the same web server. They're just alias web links.
You must have a valid Intermediate Certificate installed on the server.
More about that: Cannot view Quicktime movies over HTTPS in Safari or UIWebView
Related
I created a web AR demo (Android Chrome) with a sound file attached. The AR with the sound works on an HTTP website, but not on HTTPS. It seems that HTTPS requires user interaction to do so. I just wonder how Google did this with their AR animals (i.e. search for "Tiger" in Google and use the AR button). Unfortunately, there is no documentation on their website about the audio implementation.
How can I get this working on an HTTPS website?
<model-viewer src="assets/my3DModel.glb?sound=assets/mySound.ogg"...
Development Source: https://modelviewer.dev
I have created a basic web page that links to a few YouTube accounts. Each account has a custom URL as allocated by Google via Google+:
http://www.youtube.com/c/*channelName
The links work fine in iOS Safari and offers to open the YouTube app, which is the behaviour that I want, but when I click the links in iOS Chrome it simply sends me to the mobile YouTube website.
Anyone know why Chrome doesn't launch the YouTube app? Normally if you click a YouTube link in Chrome it does it by default, but I can't get it to work with this particular URL format.
Try this:
Open settings in iOS Chrome
Google Apps
Turn on YouTube
YouTube was off by default on my iPhone.
I noticed this web browser, Photon (iTunes Store link) is able to play flash. My question is, if Apple doesn't allow flash to run on devices and all web browsers must use Apple's UIWebView, how can this app enable Flash playback?
Most third party apps route flash video to a there own Server to be re-encoded to another Safari friendly file format such as mp4. Once the was bee re-encoded it sent back to there client device
My app solution on iOS has downloaded audio and video for offline use. Streaming to apple tv worked like charm for a while, however, we needed to implement file encryption. As a web app, to support encrypted file on the webview, we implemented a http server, which decrypts the file, and streams it unencrypted to the webview request. But now, we need to stream theses encrypted files to the Apple Tv, obviously, when trying to shared the video/audio, the Apple TV tries to stream from the iPad http server url (localhost:8000), and an error is shown.
How should I be able to stream it? As I see, there are other apps which uses encryption and works fine with air play.
Edit: The error message is way generic, just appears on TV that the file could not be played, no log on xcode console.
The HTML on the webview is simple as that, no big deal: <video src= "http://localhost:8000/file/fileId"/>, works fine on iPad, but not streaming to Apple TV.
I can play a video from a local resource (on the device).
I can stream a video from the unprotected internet.
I can't stream from the company intranet (either from internal or externally)
Typical secure company network. Videos are stored in SharePoint 2007 lists (but I have url to the video file).
I've tried:
MPMoviePlayerController
MPMoviePlayerViewController
UIViewView (creating html on fly using the <video> tag and video url)
and I can't get anything to work. Heck, I can't even get it to work going directly to the link in Safari on the iPad. The only thing I haven't tried doing is downloading it as a file then playing locally. Due to a host of usability issue this would not be a preferred option.
There were 2 problems.
MPMoviePlayerController doesn't support all the challenge authentication which exists in NSURLConnection. The solution is to just do a "dummy" NSURLConnection somewhere inside your secure area, have it handle all the challenges and set it to store the information for the session. From here on out, MPMoviePlayerController or other connections which don't support the ins and outs of SSL requests will use the existing session.
A valid intermediate certificate had to be installed on the server. Something I never would have figured out myself. It exists as a small item in one of the guides under Secure connections.