Skip to updates
AGGRESSIVE
ARCHIVE

Repairing account requests from the Archive

I corrected a browser request-policy problem affecting owner sign-in, username actions, forum posts, Bulletin contributions and visit recording. A reported iPhone request reached the right Archive address but arrived without a usable origin and was rejected. Same-site requests now retain the site's origin while keeping the page path and query private.

The server still rejects missing or foreign origins. Passkeys, sessions, account records and collections keep their existing scope and storage. Checks cover the original and current hosted addresses, the main .com and www. Actual passkey confirmation on a user's device still needs its own verification.

Related page / aggressivearchive.com ↗