Community discussions

MikroTik App
 
hwmonkey
Member Candidate
Member Candidate
Topic Author
Posts: 115
Joined: Wed Feb 08, 2012 9:50 pm

Redirect HTTPS to HTTP

Mon Sep 23, 2013 4:18 pm

Is there a method for the Mikrotik to intercept an HTTP (port 80) for a particular URL and redirect it to a port 443? I saw an old thread about this which said "not at this time" and then a lot of argument about why one should not do this.

In my case, it is for webmail. I do not want internal people to go to the HTTP version of webmail but force them to HTTPS. On the server side, this would be a redirect. So, can such a command be done on Mikrotik? I am thinking a script could do this...
 
iprob
Frequent Visitor
Frequent Visitor
Posts: 66
Joined: Wed Mar 07, 2012 12:44 am

Re: Redirect HTTPS to HTTP

Tue Sep 24, 2013 4:19 pm

I don't believe there is any way to do this on the MikroTik. We have the same situation and use IIS URL Rewrite to redirect to https on Exchange web servers. It is very easy to redirect from http to https on both IIS and Apache. You should approach it on the web server since nothing on the MikroTik is really designed to do it.
 
hwmonkey
Member Candidate
Member Candidate
Topic Author
Posts: 115
Joined: Wed Feb 08, 2012 9:50 pm

Re: Redirect HTTPS to HTTP

Wed Sep 25, 2013 7:25 am

I don't believe there is any way to do this on the MikroTik. We have the same situation and use IIS URL Rewrite to redirect to https on Exchange web servers. It is very easy to redirect from http to https on both IIS and Apache. You should approach it on the web server since nothing on the MikroTik is really designed to do it.
Thanks. I would if I could. So, MTK cannot do this, even using a script. Is this a definitive statement?
 
sergeysi
just joined
Posts: 13
Joined: Mon Aug 19, 2013 6:59 pm

Re: Redirect HTTPS to HTTP

Wed Sep 25, 2013 8:02 am

Here is the thing... If a client sends a request to TCP80 and you managed to redirect these packets to TCP443, then client will receive packets from TCP443 and these packets will be rejected either by standalone firewall or client's firewall because this connection was not initiated by the client. You can do this only by using webserver's Redirect instruction so the client will reinitiate connection to TCP443. Or using a proxy server (not sure if mikrotik's proxy server is able to do that).

Who is online

Users browsing this forum: jkjkrules and 31 guests