# gRPC Using HTTPS Scheme

**URL:** <https://community.postman.com/t/grpc-using-https-scheme/52202>\
**Category:** Help Hub\
**Tags:** grpc\
**Created:** [September 22, 2023, 8:34am UTC](https://community.postman.com/t/grpc-using-https-scheme/52202 "2023-09-22T08:34:24Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![nkhumphreys7](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/nkhumphreys7/32/25853_2.png) [@nkhumphreys7](https://community.postman.com/u/nkhumphreys7)\
**Post date:** [September 22, 2023, 8:34am UTC](https://community.postman.com/t/grpc-using-https-scheme/52202/1 "2023-09-22T08:34:24Z")

</div>

Hey,

I am trying to make a gRPC request to my API which is behind a cloud load balancer. The cloud load balancer is a TCP load balancer that supports HTTP/2 but, for some reason which is beyond our control, rejects any requests that do not have a HTTP/HTTPS scheme. This is currently working for clients connecting from various languages (C++, Go, Python) so even though this is odd, gRPC is working.

When I manually overwrite the scheme in the Postman request path, postman gives me the error shown here

 ![Screenshot 2023-09-21 at 09.34.56](https://us1.discourse-cdn.com/getpostman/original/3X/8/8/88344e5627ba3258417a1778ad4b9bc9a1461f00.png)

I cannot manually set the header in a gRPC request using Postman as the header tab is missing for this request type.

Is there a way to force postman to set the scheme to HTTPS for gRPC requests?

Thanks,  
Nathan

---

<div class="post-metadata">

**Author:** ![danny-dainton](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/danny-dainton/32/29401_2.png) [@danny-dainton](https://community.postman.com/u/danny-dainton)\
**Post date:** [September 22, 2023, 1:42pm UTC](https://community.postman.com/t/grpc-using-https-scheme/52202/2 "2023-09-22T13:42:25Z")

</div>

Hey @nkhumphreys7

Welcome to the Postman Community! :postman:

There’s no way to set the URL scheme (https) but a header can be set using the meta-data tab and TLS can be enabled using the lock icon toggle.

There’s no URL scheme other than grpc:// in gRPC.

---

<div class="post-metadata">

**Author:** ![nkhumphreys7](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/nkhumphreys7/32/25853_2.png) [@nkhumphreys7](https://community.postman.com/u/nkhumphreys7)\
**Post date:** [September 22, 2023, 2:10pm UTC](https://community.postman.com/t/grpc-using-https-scheme/52202/3 "2023-09-22T14:10:01Z")

</div>

> [@danny-dainton](#):
>
> but a header can be set using the meta-data tab

Hi Daniel, thanks for the reply! Setting the header via the Meta Tab is doing exactly what we want! Thanks again!

---

<div class="post-metadata">

**Author:** ![system](https://sea2.discourse-cdn.com/getpostman/user_avatar/community.postman.com/system/32/29796_2.png) [@system](https://community.postman.com/u/system)\
**Post date:** [September 25, 2023, 2:10pm UTC](https://community.postman.com/t/grpc-using-https-scheme/52202/4 "2023-09-25T14:10:13Z")

</div>

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