Open HitLuca opened 2 years ago
Also having this issue.
Came here after AWS IAM console gave errors when viewing a user. I sent them feedback about it. Turned out ClearURLs was rewriting SPA hash-based urls. Apps at my company also use these.
Why? Hash-based urls require no server-side coordination. When you use regular URLs for SPA pages, you have to mess with history APIs in the client app IIRC, and your server has to be setup to only serve files from the base path no matter what path comes after it. If not specially setup, it will return a 404 when someone follows a bookmark. Hash-based URLs avoid this.
Whitelisting would be a rough solution to this issue. There could be a lot of whitelisting to do, as this is a common approach. Ideally, ClearURLs would handle them robustly.
Also I tried to look for this issue on gitlab repo, but it wouldn't even let me search without creating an account. A bit pushy, that.
Same issue. Was tearing my hair out trying to narrow it down to this! Specifically, it's the replaceState()
protection breaking things
This also breaks the clicking into a user's account https://us-east-1.console.aws.amazon.com/iam/home#/users/mycooluser gets spam reloaded as https://us-east-1.console.aws.amazon.com/iam/home#%2Fusers%2Fmycooluser= and then the page can't load the user.
My only recourse was to disable the extension.
Also breaks Secrets Manager
It breaks any part of the AWS Console that uses ETags on URLs. Includes CloudFront but includes a large chunk of the console.
Looks like this extension breaks the behavior or the Amazon AWS AIM cloud console, since when it tries to redirect me to
https://us-east-1.console.aws.amazon.com/iam/home#/security_credentials$mfa
the url gets truncated and I cannot access the console's functionalities.Related to #137 , adding a whitelisting option would circumvent this issue