Configuration

Overview

The Web357 wwwRedirect plugin is a Joomla system plugin that controls URL redirection including www/non-www toggles, HTTPS enforcement, and domain unification. This ensures better SEO and consistent access to your site. 🔗

Basic Settings

Redirection Type

Select how the plugin handles redirection between www and non-www domain versions:

• Disabled: No redirection applied
• non-www → www: Redirect from example.com to www.example.com
• www → non-www: Redirect from www.example.com to example.com

Force HTTPS

Controls the enforcement of secure HTTPS protocol 🔒:

• Disabled: No HTTPS redirection
• http:// → https:// (Recommended): Forces secure connections
• https:// → http://: Reverts to non-secure HTTP (not recommended)

Apply Redirect on Admin

Choose whether the plugin should apply redirection rules in the Joomla admin area:

• Disabled (Recommended)
• Enabled

Advanced Settings

Exclusion Patterns

Specify paths or patterns that should be skipped from redirection. Add one pattern per line ✍️:

<code>/api/
/ipn_handler.php
/paypal_callback
/webhook
/^/admin/special/
/\.xml$/
	

Tips: Use plain strings or wrap regex patterns in /slashes/.

Enable Logging

Toggle to enable or disable logging of redirection behavior. Logs are saved to Joomla’s logs folder 🗂️.

• No: Logging disabled (default)
• Yes: Enables logging

Logs include:

• Timestamp
• Visitor IP
• Request method
• Source and destination URLs
• Matched exclusion pattern (if any)

Multi-Domain Redirection

Preferred Domain

Set your preferred domain to redirect all other aliases (e.g., dev.mydomain.com) 🌐.

Examples:

• mydomain.com
• www.mydomain.com
• shop.mydomain.com

Domain Detection Tool

Detects the domain you're currently using and lets you apply it as the preferred domain via one click 🖱️.

Example: domain.com → Set as Preferred Domain

Common Usage Scenarios

Scenario 1: Standard SEO

<code>Redirection Type: non-www → www
Force HTTPS: http → https
	

Scenario 2: Multi-Domain Consolidation

<code>Preferred Domain: www.mydomain.com
Force HTTPS: http → https
	

Scenario 3: Payment Callback Exclusions

<code>Exclusion Patterns:
/paypal_ipn
/stripe_webhook
/api/payment/
	

Redirection Priority Order

1. Exclusion Patterns 🛑
2. Preferred Domain 🌍
3. Force HTTPS 🔐
4. WWW/Non-WWW ↔️

Best Practices

• Test configuration on a staging environment 🧪
• Enable logging during setup for insights 📝
• Use exclusions for APIs and payment gateways 💳
• Ensure SSL certificate before enabling HTTPS 🔐
• Prevent redirect loops (avoid .htaccess conflict) 🔁
• Use consistent canonical domain for SEO 📈

Troubleshooting

Redirect Loops

Cause: Conflict with server (.htaccess) redirects.

Fix: Disable .htaccess rules and use plugin settings only.

Backend Access Problems

Cause: Redirects enabled for admin area.

Fix: Disable "Apply Redirect on Admin" or add admin to exclusions.

Payment Gateway Errors

Cause: Payment callback URL was redirected.

Fix: Add payment paths to the exclusion list.