Member Avatar for silent lover

i do not know if this is the correct section to post this htaccess question.
when user type example.com on browser, it redirect to https://example.com .
and when user type www.example.com on browser, it redirect to https://example.com .
and when user type https://www.example.com on browser, it redirect to https://example.com .
and when user type http://example.com or http://www.example.com on browser, it redirect to https://example.com .
how to create htaccess for that?

regards,
silent lover

  • 2 Contributors
  • 2 Replies
  • 115 Views
  • 2 Days Discussion Span
  • Latest Post Latest Post by silent lover

Dani AI

Generated

For : a compact, reliable .htaccess solution that sends every request (http, https, www or non‑www) to the single canonical URL https://example.com using a single 301 when possible. Thanks to for the pointers — the snippet below is simple to drop into your site root and includes common troubleshooting notes.

RewriteEngine On

# 1) If host starts with "www.", send to https://non-www (handles http and https)
RewriteCond %{HTTP_HOST} ^www\.(.+)$ [NC]
RewriteRule ^ https://%1%{REQUEST_URI} [L,R=301]

# 2) If request is not HTTPS (and host is already non-www), send to https://
RewriteCond %{HTTPS} off
RewriteRule ^ https://%{HTTP_HOST}%{REQUEST_URI} [L,R=301]

If you control Apache config, prefer a port 80 VirtualHost redirect (less overhead):

<VirtualHost *:80>
  ServerName example.com
  ServerAlias www.example.com
  Redirect 301 / https://example.com/
</VirtualHost>

Notes and troubleshooting:

  • Test with temporary 302 redirects first (change R=301 to R=302) while verifying behavior and avoiding cached 301s. Use curl -I -L http://www.example.com to inspect the chain.
  • If behind a proxy/load balancer that terminates SSL, %{HTTPS} may be off; check X-Forwarded-Proto instead and redirect when it is not https.
    RewriteCond %{HTTP:X-Forwarded-Proto} !https
RewriteRule ^ https://example.com%{REQUEST_URI} [L,R=301]
  • Enable mod_rewrite and watch for redirect loops (clear browser cache when retesting). Consider HSTS only after redirects are correct; see the Short‑Term testing advice on HSTS.

For implementation details, see the Apache mod_rewrite docs and the MDN page on Strict-Transport-Security:
Apache mod_rewrite docs
Strict-Transport-Security (MDN)

Recommended Answers

All 2 Replies

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.