English version
APEX supports Friendly URLs and the legacy f?p syntax. Understanding the URL helps when diagnosing navigation and unexpected session values.
The legacy structure separates application, page, session, request, debug, clear-cache, item names, and item values with colons. A missing separator can shift a value into the wrong position. Prefer declarative link builders and supported URL-generation APIs to manual concatenation.
Treat values received through a URL as user-controlled input. Apply server-side validation and authorization, and preserve the application's URL protection requirements. A request value used for a rendering condition does not by itself perform a page submit or authorize a write operation.
Clear cache deliberately: understand which session values should be reset before the target page renders. Keep private information and credentials out of URLs, and avoid distributing live session identifiers.
When debugging a link, check the generated destination, intended page, cleared state, and the values the server actually receives.
Reference: Oracle URL syntax.
