Security Vulnerabilities Guide

Understanding and fixing common web security vulnerabilities detected by VitaPulse

High

No HTTP to HTTPS Redirect

Your server does not redirect HTTP requests to HTTPS, allowing users to access the site over an insecure connection.

Risk

Even if your site supports HTTPS, users who type your URL without 'https://' or follow old HTTP links will access the unencrypted version. All their data is exposed. Search engines may also index the HTTP version, creating duplicate content issues and reducing your SEO ranking.

Solution

Configure a permanent (301) redirect from HTTP to HTTPS on your server. This ensures all visitors use the encrypted connection regardless of how they reach your site.

Example

# Apache .htaccess
RewriteEngine On
RewriteCond %{HTTPS} off
RewriteRule ^(.*)$ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

MDN - Redirections

Comments (0)

No messages yet.