Yes, it should be possible, if the web-server serves on the default HTTPS port (443) and provides it's a certificate (For SSL/TLS) it can be self signed or purchased one. Even the port 443 is not mandatory, you can use https://web-service-service:<custom-https-port>. So the web-app-service must provide a full fledged HTTPS support, the client can then use https instead of http.
But most of the architectures don't implement HTTPs in the web-server itself, instead they use a reverse-proxy with HTTPS configured. It is called TLS termination. Only the reverse-proxy will be exposed to the public.
Yes, it should be possible, if the web-server serves on the default HTTPS port (443) and provides it's a certificate (For SSL/TLS) it can be self signed or purchased one. Even the port 443 is not mandatory, you can use
https://web-service-service:<custom-https-port>
. So the web-app-service must provide a full fledged HTTPS support, the client can then use https instead of http.But most of the architectures don't implement HTTPs in the web-server itself, instead they use a reverse-proxy with HTTPS configured. It is called TLS termination. Only the reverse-proxy will be exposed to the public.
Thanks a lot for this.
Do you mind sharing any resource on this?