HTTP to HTTPS on the same port

vzxen · 03-22-2011, 11:18 AM

Hi,

I want to ENABLE SSL on a PORT 2222 :
Listen 2222
<VirtualHost *:2222>
ServerName localhost
DocumentRoot /usr/local/path
SSLEngine on
SSLCertificateFile /usr/local/path/conf/path.crt
SSLCertificateKeyFile /usr/local/path/conf/path.key
SSLCertificateChainFile /usr/local/path/conf/path-bundle.crt
</VirtualHost>

Now this works fine. But I also want the HTTP URL to work and redirect it to HTTPS.
When I visit http://IP:2222 I get :

Quote:

Bad Request

Your browser sent a request that this server could not understand.
Reason: You're speaking plain HTTP to an SSL-enabled server port.
Instead use the HTTPS scheme to access this URL, please.

Hint: https://localhost/

How should I make this request of http://IP:2222 REDIRECT to https://IP:2222

SL00b · 03-22-2011, 11:25 AM

It's not possible to have http and https on the same port, because different port assignments are the only way the server knows which language to speak.

rgdacosta · 03-22-2011, 11:40 AM

Both the browser and the server will be confused by this. The browser sends a HTTP request, the server then gets an invalid HTTPS request, so it's not strange you get HTTP error 400 (bad request).

Instead, use mod_rewrite on the Apache server to force HTTPS. Something like:

RewriteCond %{SERVER_PORT}!^443$
RewriteRule ^(.*)$ https://www.domain.com

vzxen · 03-22-2011, 02:30 PM

Hi,

I tried the RewriteRules but its not working !

Code:

Listen 2222
<VirtualHost *:2222>
ServerName localhost
DocumentRoot /usr/local/path
SSLEngine on
SSLCertificateFile /usr/local/path/conf/path.crt
SSLCertificateKeyFile /usr/local/path/conf/path.key
SSLCertificateChainFile /usr/local/path/conf/path-bundle.crt

RewriteEngine On 
RewriteCond %{HTTPS} off 
RewriteRule ^http\:(.*)$ https:$1 [P]

</VirtualHost>

Any idea ???
Is it not POSSIBLE to send a REDIRECT Header to point them https://ip:2222/

rgdacosta · 03-22-2011, 02:40 PM

Have you installed mod_rewrite?

/usr/lib/httpd/modules/mod_rewrite.so

Basically, your client's requests for http:// is converted to https://

I use that when I want to force https://

grzesiek · 03-22-2011, 02:57 PM

Why not use iptables REDIRECT 80/tcp -> 2222/tcp?

vzxen · 03-22-2011, 03:10 PM

Hi,

mod_rewrite is enabled.
Had it not been Apache would have not started right ?
IPTABLES is not what I want to play with for this.

How should I redirect the Browser ?
Is there something wrong in My Virtualhost ?

Slackyman · 03-22-2011, 03:23 PM

Try

Code:

Listen 2222
<VirtualHost *:2222>
ServerName localhost
DocumentRoot /usr/local/path
SSLEngine on
SSLCertificateFile /usr/local/path/conf/path.crt
SSLCertificateKeyFile /usr/local/path/conf/path.key
SSLCertificateChainFile /usr/local/path/conf/path-bundle.crt
RewriteEngine On 
RewriteCond %{HTTPS} off 
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R,L]
</VirtualHost>

vzxen · 03-23-2011, 04:01 AM

Hi,

@Slackyman even that is now working
How should we do this ?

Is it not possible to enable SSLEngine on condition of :
%{HTTPS} on

vzxen · 03-23-2011, 11:25 AM

Hi,

Please can someone help me.
My apache error logs also does not show anything.

bathory · 03-23-2011, 01:35 PM

Hi,

You should put the rewrite stuff in a .htaccess in the DocumentRoot (/usr/local/path), or inside a <Directory /usr/local/path>...</Directory> stanza in httpd.conf

Regards

Slackyman · 03-24-2011, 04:31 AM

Quote:

Originally Posted by vzxen

Hi,

@Slackyman even that is now working
How should we do this ?

Is it not possible to enable SSLEngine on condition of :
%{HTTPS} on

Sorry, maybe I was drunk

vzxen · 03-24-2011, 08:02 AM

Hi,

@bathory

Quote:

Listen 2222
<VirtualHost *:2222>
ServerName localhost
DocumentRoot /usr/local/path
SSLEngine on
SSLCertificateFile /usr/local/path/conf/path.crt
SSLCertificateKeyFile /usr/local/path/conf/path.key
SSLCertificateChainFile /usr/local/path/conf/path-bundle.crt
<Directory /usr/local/virtualizor>
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}/$1 [R,L]
</Directory>
</VirtualHost>

I still get the 400 bad request.

bathory · 03-24-2011, 08:14 AM

Quote:

Originally Posted by vzxen

Hi,

@bathory

I still get the 400 bad request.

You must not put it in the ssl vhost definition.
It's supposed to work with the non-ssl server, so when you get a http request, so it turns it into https

16pide · 03-24-2011, 11:24 AM

I believe the solution is described in http://webdesign.about.com/od/metata.../aa080300a.htm