Why QCTNH Does Not Follow Arbitrary URLs or Redirects

The production QCTNH worker deliberately avoids arbitrary URLs and redirect chains; it calls the exact validated Joomla WebCron endpoint registered for the site.

No arbitrary redirect following

The worker uses cURL with redirect following disabled. A 301/302 response is therefore not silently followed to a new host/path. Register the final canonical native WebCron URL instead.

Why this is safer

• Prevents a once-valid endpoint from redirecting the worker to an unrelated host.
• Keeps the registered origin/route security checks meaningful at execution time.
• Makes HTTP→HTTPS/domain/subdirectory migrations explicit instead of hiding them behind redirects.

If you receive a redirect response

Fix Joomla/server canonical routing, open the final canonical URL, run Check WebCron, then Test Connection so the service stores the actual final route. Do not try to solve it by enabling redirect following.

Secrets and diagnostics

When troubleshooting Why QCTNH Does Not Follow Arbitrary URLs or Redirects, prefer status codes, readiness states, hashes/“matches” indicators, and sanitized activity messages over copying raw secrets. The Joomla WebCron key and QCTNH service credential are operational credentials, not ordinary configuration text for screenshots or public discussion.

If compromise is suspected, rotate the WebCron key and resynchronize rather than trying to keep an exposed credential active.

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.