# How to allow both http and https HLS traffic to the same wowza application

**URL:** <https://community.wowza.com/t/how-to-allow-both-http-and-https-hls-traffic-to-the-same-wowza-application/39246>\
**Category:** Wowza Streaming Engine\
**Created:** [November 15, 2012, 12:09pm UTC](https://community.wowza.com/t/how-to-allow-both-http-and-https-hls-traffic-to-the-same-wowza-application/39246 "2012-11-15T12:09:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Erik\_Manor](https://avatars.discourse-cdn.com/v4/letter/e/3bc359/32.png) [@Erik\_Manor](https://community.wowza.com/u/Erik_Manor)\
**Post date:** [November 15, 2012, 12:09pm UTC](https://community.wowza.com/t/how-to-allow-both-http-and-https-hls-traffic-to-the-same-wowza-application/39246/1 "2012-11-15T12:09:13Z")

</div>

Hi,

I have setup Wowza to use SSL. Currently the only player were are concerned with for SSL access is HLS. When I access a playlist URL via SSL the initial connection happens over SSL, but the URL’s returned for the chunklist(s) are http. So I found this property on the forum.

cupertinoPlaylistHostProtocol

https://

which works. The problem is if a client accesses the original playlist URL via http, all the chunklist URL(s) will be returned as https. What we are looking for is if the original playlist request is http, then all requests (chunklist and .ts files) should happen over http. If the original request is https then all requests (chunklist and .ts files) should happen over https.

Currently the only way to accomplish this is with separate wowza applications which we are trying to avoid. Is there another way to do this? For example I thought I could manipulate the playlist depending on what the original request protocol was, but I don’t see a way to do this with possible exception of using a playlist delegate for DVR. This wouldn’t help for Live and VOD. Are there any modules or configurations I can make to accomplish our requirements?

Thanks in Advance,

erik

---

<div class="post-metadata">

**Author:** ![Richard\_Lanham](https://avatars.discourse-cdn.com/v4/letter/r/c68b51/32.png) [@Richard\_Lanham](https://community.wowza.com/u/Richard_Lanham)\
**Post date:** [November 15, 2012, 11:16pm UTC](https://community.wowza.com/t/how-to-allow-both-http-and-https-hls-traffic-to-the-same-wowza-application/39246/2 "2012-11-15T23:16:49Z")

</div>

erik,

I don’t think there is a way around this using this property

Richard

---

<div class="post-metadata">

**Author:** ![Tapan\_Thapa](https://avatars.discourse-cdn.com/v4/letter/t/f1d935/32.png) [@Tapan\_Thapa](https://community.wowza.com/u/Tapan_Thapa)\
**Post date:** [February 1, 2017, 10:21pm UTC](https://community.wowza.com/t/how-to-allow-both-http-and-https-hls-traffic-to-the-same-wowza-application/39246/3 "2017-02-01T22:21:59Z")

</div>

> erik,
> 
> I don’t think there is a way around this using this property
> 
> Richard

In 2017, is it possible to implement this feature now?

---

<div class="post-metadata">

**Author:** ![Jermaine\_Hemby](https://avatars.discourse-cdn.com/v4/letter/j/82dd89/32.png) [@Jermaine\_Hemby](https://community.wowza.com/u/Jermaine_Hemby)\
**Post date:** [February 18, 2017, 7:40am UTC](https://community.wowza.com/t/how-to-allow-both-http-and-https-hls-traffic-to-the-same-wowza-application/39246/4 "2017-02-18T07:40:25Z")

</div>

Hello,

Thanks for contacting Wowza Forums!

You can check for feature updates here:

[https://www.wowza.com/docs/wowza-streaming-engine-software-updates](https://www.wowza.com/docs/wowza-streaming-engine-software-updates)

regards,

Jermaine