# Zoom SDK web endpoint marked as 'http' by browsers

**URL:** <https://devforum.zoom.us/t/zoom-sdk-web-endpoint-marked-as-http-by-browsers/104412>\
**Category:** Web\
**Created:** [February 22, 2024, 4:38pm UTC](https://devforum.zoom.us/t/zoom-sdk-web-endpoint-marked-as-http-by-browsers/104412 "2024-02-22T16:38:48Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![godwin.owonam](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/godwin.owonam/32/53602_2.png) [@godwin.owonam](https://devforum.zoom.us/u/godwin.owonam)\
**Post date:** [February 22, 2024, 4:38pm UTC](https://devforum.zoom.us/t/zoom-sdk-web-endpoint-marked-as-http-by-browsers/104412/1 "2024-02-22T16:38:48Z")

</div>

**Description**  
I am having issues with running my SDK implementation on most OS’s including Desktop and mobile devices. The issues range from devices not being allowed (blocked camera, and blocked audio), to the application not even starting.

When I checked site settings I found out that the zoom endpoint was in ‘http’. This is supposed be ‘https’ in my opinion and is the reason for the devices not being allowed for the site/app.

Is there a walk around? Or I’m I missing something?

**Which Web Video SDK version?**  
1.9.5

**Screenshots**  
 ![Screenshot from 2024-02-22 21-28-04](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/e/4/e469d8f60f82ae870fc8cd5e36d920dfb781980e.png)

---

<div class="post-metadata">

**Author:** ![rehema.zoom](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/rehema.zoom/32/40323_2.png) [@rehema.zoom](https://devforum.zoom.us/u/rehema.zoom)\
**Post date:** [February 26, 2024, 4:05pm UTC](https://devforum.zoom.us/t/zoom-sdk-web-endpoint-marked-as-http-by-browsers/104412/2 "2024-02-26T16:05:40Z")

</div>

Hi @godwin.owonam ,

Are you running into these issues when testing with our [sample application](https://github.com/zoom/videosdk-web-sample)?

thanks,  
Rehema

---

<div class="post-metadata">

**Author:** ![godwin.owonam](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/godwin.owonam/32/53602_2.png) [@godwin.owonam](https://devforum.zoom.us/u/godwin.owonam)\
**Post date:** [February 26, 2024, 4:20pm UTC](https://devforum.zoom.us/t/zoom-sdk-web-endpoint-marked-as-http-by-browsers/104412/3 "2024-02-26T16:20:45Z")

</div>

Hi @rehema.zoom  
Thanks for responding.

The sample application was modified to suit our requirements and I believe that is the aim of having a sample application.

However, we hosted the application and we are using the hosted application (from a https server) in an iFrame on a webpage.

I don’t know if there is anything wrong with that (just informing).

I appreciate your feedback.  
Please enlighten us where the source of the problem may be.

Thanks,  
Godwin @godwin.owonam

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [February 27, 2024, 2:29am UTC](https://devforum.zoom.us/t/zoom-sdk-web-endpoint-marked-as-http-by-browsers/104412/4 "2024-02-27T02:29:46Z")

</div>

Hey @godwin.owonam

The connection between the Video SDK and the Zoom server always requires the HTTPS or WSS protocol.

Could you please check if it’s your network policy (typically the proxy server) that is causing the switch to the HTTP protocol?

Thanks  
Vic

---

<div class="post-metadata">

**Author:** ![godwin.owonam](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/godwin.owonam/32/53602_2.png) [@godwin.owonam](https://devforum.zoom.us/u/godwin.owonam)\
**Post date:** [February 28, 2024, 10:40am UTC](https://devforum.zoom.us/t/zoom-sdk-web-endpoint-marked-as-http-by-browsers/104412/5 "2024-02-28T10:40:48Z")

</div>

Hi @vic.yang

After troubleshooting for some time, I find that the issue comes from the cookies used by [zoom.us](http://zoom.us). It appears the SameSite attribute has not been set at all in the cookies. This should be the cause of the issue.

Hence, because the SameSite attribute is not set, the browser defaults it to ‘Lax’ and blocks the cookies, and the application cannot start.

Please see attached screenshots.

 ![Screenshot from 2024-02-28 16-03-39](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/4/3/4392deb0155e30ef8024d8a2175a38249c2d1b08.png)

As you can see, below, these cookies are marked as affected cookies on the browser:

 ![Screenshot from 2024-02-28 16-04-16](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/9/c/9cf4a0d816888f538a095003217547c7917af96c.png)

---

<div class="post-metadata">

**Author:** ![vic.yang](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/vic.yang/32/24656_2.png) [@vic.yang](https://devforum.zoom.us/u/vic.yang)\
**Post date:** [February 29, 2024, 9:33am UTC](https://devforum.zoom.us/t/zoom-sdk-web-endpoint-marked-as-http-by-browsers/104412/6 "2024-02-29T09:33:51Z")

</div>

Hey @godwin.owonam

These cookies are unrelated to the functionality of the Video SDK; they simply record some preference settings on the Zoom website. Could you please take another look to see if any other reasons are causing HTTP-related issues?

> **[Spiegazione dei cookie SameSite  |  Articles  |  web.dev](https://web.dev/articles/samesite-cookies-explained?hl=it)**
>
> Scopri come contrassegnare i cookie per l'utilizzo proprietario e di terze parti con l'attributo SameSite. Puoi migliorare la sicurezza del tuo sito utilizzando i valori Lax e Strict di SameSite per migliorare la protezione dagli attacchi CSRF. Se...

Thanks  
Vic

---

<div class="post-metadata">

**Author:** ![godwin.owonam](https://sea2.discourse-cdn.com/flex016/user_avatar/devforum.zoom.us/godwin.owonam/32/53602_2.png) [@godwin.owonam](https://devforum.zoom.us/u/godwin.owonam)\
**Post date:** [March 1, 2024, 4:08pm UTC](https://devforum.zoom.us/t/zoom-sdk-web-endpoint-marked-as-http-by-browsers/104412/7 "2024-03-01T16:08:30Z")

</div>

@vic.yang

Yes, you are right. The issue was related to CORS since our SDK was hosted in an IFrame provided in a domain different from our main domain.

Thanks.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex016/uploads/zoomdeveloper/original/3X/6/1/614bdd549b610bbaa46ff934617683a02bdaa03c.png) [@system](https://devforum.zoom.us/u/system)\
**Post date:** [April 1, 2024, 2:08am UTC](https://devforum.zoom.us/t/zoom-sdk-web-endpoint-marked-as-http-by-browsers/104412/8 "2024-04-01T02:08:53Z")

</div>

Closed on April 1, 2024, 2:08am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.
