ShoxiousOriginal post
Rank 2: Process
I am using Angular with hash routing and receive a link after registration. In this example, it is localhost: http://localhost:4200/?userId=655c3eeeb315974d5b07&secret=7084d9b9ad01b32f6c257fd8752e0966b8c4092e2edf11f278b08453f759b01dd65ffc869eb875bd2a8145b0566d43a4f1447fb8ad73fb1fdab72a5ec1e5e9fb8c46466af9aaa38855aa14011f984978dca8bd0233c47956119cfe458f5f24a208adaf2fb9f55d630cd8a2b78250a7292d99bfffa1619600a74a6d378760ba3e&expire=2023-11-28+05%3A23%3A59.250#/verify
Appwrite modifies my URL and places the parameters userId, secret, and expire between my hash. How can I solve this problem so that the parameters come after /#/verify?
Summary
The user is using Angular with hash routing and is receiving a URL after registration. The problem is that Appwrite modifies the URL and places the parameters between the hash. The user wants the parameters to come after /#/verify.
One suggestion is to change the routing strategy to use the path strategy instead of the hash strategy. The user can refer to the Angular documentation for more information on how to do this.
Another user suggests that according to the RFC for URLs, fragments should go at the end, which is why they end up after the hash. They mention avoiding the hash strategy for this reason.
Lastly, another user recommends raising the issue on