- Shipped
- 5 செப்டம்பர், 2026 அன்று 6:43 AM UTC
- Author
- Kamo
- Commit
- ccf8228
The endpoints prefer the query parameter, but they are deployed separately from this code, and a browser that loads the new bundle a minute before EmailService rolls over would have addressed every folder as "~". That is not a Gmail-shaped regression — it is every folder, for everyone, for the length of the window. So the path carries the real name whenever the name can reach a handler intact, and stands aside only for one that cannot: a "/" or "%" or "\" or ";" the container and StrictHttpFirewall refuse, or a "+" that the old path form's second decode would silently read as a space. Those are exactly the names that were already failing, so nothing that works today stops working in either direction. It also leaves the ordinary URL readable in a log, which "~" does not.