topic Then you need to find a in Network Security

Cisco ASA rely HTTP port to HTTPS without using CNAME DNS-record

Vadim Semenov — Tue, 12 Mar 2019 04:22:27 GMT

Hi all,

could anyone tell me Is it possible to configure ASA so when customer rely http://domain.com Cisco ASA rely to https://domain.com (it's similar with CName function of domain record).

P.S. resource of domain.com located behind ASA and DNS A-record rely on public ASA ip address

Thank you.

The ASA can not do this

Marius Gunnerud — Wed, 25 Jun 2014 10:26:17 GMT

The ASA can not do this redirect based on URL/FQDN. You would need to find another way of doing it.

Please remember to select a correct answer and rate helpful posts

What version ASA are you

Marius Gunnerud — Wed, 25 Jun 2014 10:42:50 GMT

What version ASA are you running?

If the server has both static public and private IPs you could use NAT to redirect HTTP traffic to HTTPS based on IP.

object network PUBLIC_IP
host 1.1.1.1

object network REAL_IP
host 2.2.2.2
nat (inside,outside) static PUBLIC_IP http https

Keep in mind that you will also need a NAT statement that maintains https to the server.

Please remember to select a correct answer and rate helpful posts

Hello, Marius,thank you for

Vadim Semenov — Thu, 26 Jun 2014 06:04:31 GMT

Hello, Marius,

thank you for your reply. I understand that we should find another way of doing it.

From your example follow what server must work with http protocol and after ASA it will be already https protocol?

In my example above, any http

Marius Gunnerud — Thu, 26 Jun 2014 06:21:23 GMT

In my example above, any http traffic that is destined for public IP 1.1.1.1 will be translated to the private IP of 2.2.2.2 and the port will be translated to https.

http to 1.1.1.1 --> https to 2.2.2.2

Please remember to select a correct answer and rate helpful posts

Ok, but it highly neccessery

Vadim Semenov — Thu, 26 Jun 2014 06:34:44 GMT

Ok, but it highly neccessery to force customer using https until ASA, and it not very critical what we using https inside network.

Then you need to find a

Marius Gunnerud — Thu, 26 Jun 2014 06:36:50 GMT

Then you need to find a different solution...you might want to look at solutions such as clientless SSL VPN, Citrix, or similar.

Please remember to select a correct answer and rate helpful posts