Answers.Body: <p>Personally, I would just go with S3 (I've <a href="https://craftcms.stackexchange.com/a/578/258">ranted</a> about this before), but I understand that sometimes your hand is forced.</p>
  
  <p>I was not even aware that Rackspace supported SSL or that it would be a different domain. I did some digging through their docs and it seems there'll be some work involved to get this feature in and it will cause a change in behaviour, so I'd say this will have to wait until 2.2.</p>
  
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-23T19:39:14.460Z
Answers.Text: For most projects, S3 is the choice. However, hands are forced and Rackspace is required. Is there any way you guys can add hook to manipulate asset urls in the meantime?
Answers.UserDisplayName: Wes Rice
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-24T05:28:37.323Z
Answers.Text: Okay, so let's try the simple way. What's stopping you from going into Rackspace MyCloud console, looking up the container HTTPS URL there and just use that in your Source settings?
Answers.UserDisplayName: Andris Sevcenko
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-24T13:44:03.110Z
Answers.Text: Good point. Not every environment uses the SSL. So I'm guessing I should be able to put the appropriate container url in my 'environmentVariables' array in general.php and be able to utilize that variable in the source settings?
Answers.UserDisplayName: Wes Rice
Answers.ContentLicense: CC BY-SA 3.0
Answers.CreationDate: 2014-07-23T18:51:20.127Z
Answers.LastActivityDate: 2014-07-23T18:51:20.127Z
Answers.LastEditDate: 2017-04-13T12:51:00.303Z
Answers.UserDisplayName: Andris Sevcenko
Body: <p>How does one go about serving asset files stored in cloud locations over SSL?</p>
  
  <p>For S3, serving assets over SSL is simply a matter of changing 'http' to 'https'. However, Rackspace uses completely different domains for their SSL. This creates a situation where <a href="http://container1.rscf.com/myfile.jpg" rel="nofollow">http://container1.rscf.com/myfile.jpg</a> mightb be served over <a href="https://weird.something.rscf.com/myfile.jpg" rel="nofollow">https://weird.something.rscf.com/myfile.jpg</a>.</p>
  
  <p>There just seems like there should be a property in the getUrlForFile method in AssetsService.php that helps with this, but I'm not seeing it.</p>
  
Tags: <assets>
Title: Serving Cloud Assets over SSL
ThreadText: # Serving Cloud Assets over SSL
  
  (Asked by: username_0 on 2014-07-23)
  
  How does one go about serving asset files stored in cloud locations over SSL?
  
  For S3, serving assets over SSL is simply a matter of changing 'http' to 'https'. However, Rackspace uses completely different domains for their SSL. This creates a situation where <http://container1.rscf.com/myfile.jpg> mightb be served over <https://weird.something.rscf.com/myfile.jpg>.
  
  There just seems like there should be a property in the getUrlForFile method in AssetsService.php that helps with this, but I'm not seeing it.
  
  **Tags:** assets
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2014-07-23. Score: 3
  
  Personally, I would just go with S3 (I've [ranted](https://craftcms.stackexchange.com/a/578/258) about this before), but I understand that sometimes your hand is forced.
  
  I was not even aware that Rackspace supported SSL or that it would be a different domain. I did some digging through their docs and it seems there'll be some work involved to get this feature in and it will cause a change in behaviour, so I'd say this will have to wait until 2.2.
  
  > **Comments:**
  > **username_0**: For most projects, S3 is the choice. However, hands are forced and Rackspace is required. Is there any way you guys can add hook to manipulate asset urls in the meantime?  
  > **username_1**: Okay, so let's try the simple way. What's stopping you from going into Rackspace MyCloud console, looking up the container HTTPS URL there and just use that in your Source settings?  
  > **username_0**: Good point. Not every environment uses the SSL. So I'm guessing I should be able to put the appropriate container url in my 'environmentVariables' array in general.php and be able to utilize that variable in the source settings?  
  
  ---
  
  