amp-video and https

[gcovato]

Hi to all,

It is becoming a big issue for us the restriction that was applied on the urls of the video files supported by amp-video.

We have the majority of our video files on a video server that doesn't support the https urls.

Our plan was to create a amp-html version of all our articles on the server. Your restriction, applied from our point of view suddenly and without a pre clarification on the documentation, is making useless much part of our work.

We would like to ask to remove this restriction. Video files played by this component are files owned by the publishers. Why the component should check the real source using a certificate?

Thank you

Giuseppe

[cramforce]

AMP files are eventually served via HTTPS. All resources that cannot easily be proxied need to be served as HTTPS from the origin.

[gcovato]

It is a constraint that I didn't find in the documentation and I didn't think was planned.

[cramforce]

@gcovato Right, which is why we are doing the preview to find the things that aren't fleshed out yet. Sorry about that!

[gcovato]

Just a note

This point will force us to remove all video content from amp pages unless we find a solution.

As you understand this is not just a clarification but it has a big impact on our development and something should be explained to the publisher.

If you add to this point the fact that you didn't start the collaboration and we cannot develop our components to overcome some restriction, as you understand, we are stuck in the problems. Video component is an example.

[cramforce]

A custom component would still need to access video via HTTPS.

[gcovato]

I have HTTPS support, at least, on brightcove content but it is not supported
We developed an AMP component that uses brightcove API via JsonP but we cannot test it

[cramforce]

Note, that AMP component must not reference third party APIs or JSONP.
Would need to work similar to the Twitter embed.

On Tue, Sep 22, 2015 at 11:21 AM gcovato notifications@github.com wrote:

I have HTTPS support, at least, on brightcove content but it is not
supported
We developed an AMP component that uses brightcove API via JsonP but we
cannot test it

—
Reply to this email directly or view it on GitHub
#260 (comment).

[gcovato]

This is the place where we created our amp component for Brightcove Video.

https://github.com/gcovato/amphtml/tree/master/extensions/amp-bcvideo

[cramforce]

Looks great! Do you have a contact from Brightcove who could help with the
review?

We'd need to switch from JSONP to a CORS based API.

On Fri, Oct 2, 2015 at 3:24 AM GiCo notifications@github.com wrote:

This is the place where we created our amp component for Brightcove Video.

https://github.com/gcovato/amphtml/tree/master/extensions/amp-bcvideo

—
Reply to this email directly or view it on GitHub
#260 (comment).

[dmlap]

Just stumbled on this-- I work at Brightcove. I'm getting a 404 on @gcovato's example page right now but would be happy to find the right person to review anything if it comes back up.

[gcovato]

@dmlap the repository was private. You should be able to access it now. I opened a support ticket for getting the needed help.