Dashboards and URL fragments

[Ian Wienand]

Hello,

We recently upgraded to 3.3 and I was helping a user who has a
dashboard setup via a 302 redirect that was apparently working with
3.2.

The Location: header on the redirect sends to a complex dashboard like

https://.../#/dashboard/...

which is as documented [1]. After a bit of fiddling to simplify it, I
think this is the URL fragment. e.g. if you try

https://gerrit-review.googlesource.com/#/dashboard/?title=Mine&foreach=owner:self&My+Pending=is:open&My+Merged=is:merged

I get a blank page. However,

https://gerrit-review.googlesource.com/dashboard/?title=Mine&foreach=owner:self&My+Pending=is:open&My+Merged=is:merged

works as expected. (for reference, the dashboard on our site was
https://bit.ly/3mM3tm6 -- it does not show a blank page, the headers
are there but the query is weirdly wrong).

What I notice that the "/#/dashboard" URL quickly updates itself to
"/dashboard" -- it must be polygerrit doing this client side, as
nothing is hitting the server (I was watching our apache front-end
with our dashboard query)?

This makes me suspect something about the fragment handling is going
wrong? I looked through the changelogs but didn't notice anything.
Any suggestions where in polygerrit this "url swizzle" might happen?

Should dashboards still be using the fragment URL?

Thanks

-i

[1] https://gerrit-review.googlesource.com/Documentation/user-dashboards.html