Access now correctly preserves URL fragment characters (/, ?, =, &, ;) when redirecting users back to an application after login. Previously, these characters were encoded with encodeURIComponent, which mangled fragment-based routes used by single-page applications (SPAs).
For example, an SPA URL like https://app.example.com/#/dashboard?tab=settings&view=advanced would previously redirect to a broken URL after login. This is now handled correctly.
If your SPA users were experiencing broken navigation after authenticating through Access, this fix resolves the issue without any configuration changes.
Source: Cloudflare
Latest Posts
- AWS End User Messaging and Amazon SES now offer AI agent skills for the AWS MCP Server

- Amazon EC2 M8i and M8i-flex instances are now available in additional regions

- Amazon EC2 R8i and R8i-flex instances are now available in additional regions

- Amazon EC2 C8i and C8i-flex instances are now available in additional regions







