How QCTNH Treats www and Non-www Hostnames

QCTNH treats the www and non-www forms of the same hostname as equivalent for normal local origin comparison, reducing false migration warnings during canonical-host normalization.

Equivalent example

https://www.example.com and https://example.com are treated as the same host identity when scheme and base path otherwise match. The local comparison normalizes away a leading www..

What still must match locally

• Scheme (HTTP vs HTTPS).
• Normalized hostname after removing leading www.
• Base path/subdirectory.
• Supported/default port expectations.

Do not use www equivalence to ignore a real move

A different domain, HTTP/HTTPS change, or path move is still a meaningful origin change. If that change is intentional, open QCTNH on the intended canonical URL and use Test Connection so the change is explicitly confirmed and the service endpoint is rebuilt.

What should remain unchanged

During How QCTNH Treats www and Non-www Hostnames, Joomla Scheduled Task definitions remain owned by Joomla and their extensions. QCTNH identity rotation does not rewrite task recurrence or choose new task IDs. Likewise, a same-domain restore may preserve QCTNH identity while separately changing task next-execution/lock timestamps because those values came from the restored Joomla database.

Review both layers after migration: service identity/connectivity and scheduler queue state.

Community Discussion

Want to compare scheduler workflows, share practical tips, or discuss how you use this QCTNH feature? Visit the QC Task Nudge & Health Community. For private support, bug reports, account-specific issues, or feature requests, use the QuantaCade support system.