Skip to content
Corex

AccessRequestFlash

Corex\Config\Access\AccessRequestFlash · class · Config layer

What a failed access-request submission has to carry across the redirect (spec 079, FR-011). Only failures need this. The success path is read back out of the database, so refreshing, bookmarking or returning tomorrow all show the same truthful state and nothing can be faked by editing the URL. The stored value is user-bound (the key contains the user ID), short-lived, and read once — take() deletes before returning, so a second tab cannot show the first tab’s error and a back-button revisit shows the plain form rather than a stale complaint. The reason travels here rather than in the query string because it is the requester’s own words, and a query string is logged by the web server, kept in browser history, and forwarded in Referer headers.

Public API

Section titled “Public API”

store(int $userId, string $problem, string $reason, string $reference): void

Section titled “store(int $userId, string $problem, string $reason, string $reference): void”

take(int $userId): ?array

Section titled “take(int $userId): ?array”