Posted by Apfel007 on May 6, 2009 at 2:19pm
Jump to:
| Project: | CDN2 Video |
| Version: | 6.x-1.8 |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
Hi,
could it be, that there is a connection-problem, if I use https? I get no videos back?
I tried to get a new token with https, but the system ignored my form.
Did someone use this with https?
Cheers
Comments
#1
Try using 1.4 release if this is still an issue, please re-open.
I had major CVS trouble, but it seems to be resolved :)
#2
Hi Kyle,
I tried now several ways , but it seems to that the problem with https is still existing.
I tried the 1.4 and the dev.
I got no video back, only if I disable https during uploading and receiving :-(. If I turn https later on the video is still there - curious?!!
Cheers Kai
#3
Kai,
Are you using a self-signed certificate? If so, the backend will not connect to return status on the transcoded video.
#4
Hi acstewart,
I don't self-signed a certificate. I'm using one of my provider. The certificate is from COMODO CA Limited.
How can I find out if is the right one for cdn2?
Cheers Kai
#5
Kai, There's no "right one for cdn2".. The problem is that CDN2 won't auto-accept certificates. I'd recommend setting up an exclusion for /xmlrpc.php so that it doesn't go over ssl. This shouldn't be a security issue for cdn2's callback as the request itself is signed with a temporary key.
Regards,
-=Aaron
#6
Hi Aaron,
ok no https with cdn2..
could you give me a hint how I can solve this with the xmlrpc.php?
exclude request of cdn2 server...
thanks Kai
#7
Any hint? What way I have go? What I have to search for?
#8
bump
#9
Notification fail :)
So you'll have to add an exclude in your httpd server config for xmlrpc.php so that it doesn't require https
In apache, you can use a rewrite to exclude xmlrpc.php from https:
RewriteBase /
RewriteCond %{HTTPS} !=on
RewriteCond %{REQUEST_FILENAME} !^/xmlrpc.php
RewriteRule ^.*$ https://%{SERVER_NAME}/%1 [R=301,L]
#10
#11
Automatically closed -- issue fixed for 2 weeks with no activity.