History tries to load additional URLs separated by #! on page load. This
makes no sense on login page. However we need to preserve them when logging
in.
refs #6935
Well... I didn't want to commit this before creating single-button
forms for enabling/disabling modules. However part of this accidentally
made it through, so let's finish it.
Still some work to do, but it already looks far better like this.
refs #4095
We used to do this to blacklist certain parameters to not trigger
heavvy actions twice when navigating through history. We also do
never want to see such parameters in our address bar.
This conflicts with our slightly more complicated new filter URLs,
unless we are able to handle them on client side this is disabled
for now. IMO it should be handled server-side and eventually invol-
ving one more redirect.
There is a workaround for a nasty Chrome missbehaviour, however I have
no longer been able to reproduce it. Temporarily disabled the workaround,
could you please try whether behaviour is better / correct like this?
Please also check for requests firing twice on initial page load.
refs #6277
