How to Audit and Protect Public URLs in Osclass
Two different URL tasks in Osclass: checking whether links still work and controlling how selected public asset URLs are exposed.
Link health and URL rewriting solve different problems
A link checker asks whether an external or technical resource still responds correctly. URL rewriting changes how a selected public resource is addressed. The first is an audit task; the second is a delivery or presentation rule. Keeping them separate makes troubleshooting much easier.
Audit before you remove or rewrite anything
A marketplace can depend on payment providers, social login, analytics, security services and other external resources. A failed link report should therefore be reviewed before anything is removed automatically. The useful output is a grouped status report that lets an administrator recheck suspicious resources and keep history.
- Treat Stripe, Google, Facebook, Cloudflare and similar service URLs as functional dependencies, not clutter.
- Recheck transient failures before taking action.
- Export audit results when you need a record of the review.
Use public URL aliases narrowly
A URL alias can be useful when you want a stable public path for selected assets, but it should not become a blanket rewrite of every external or internal resource. Diagnostics are important because web-server rewrites and plugin routing can interact in unexpected ways.
Relevant TTB products
TTB Link Checker provides the audit and recheck workflow. TTB URL Shield provides controlled rewriting for selected public Osclass asset URLs. Neither product should be used as an automatic link-deletion tool.