Fixes #5194: Properly loads Bastion UI after session timeout and subsequ... #10
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
...ent redirect.
Bastion pages are driven off routes attached to the HTML anchor. The
anchor is not passed down to the web server, thus whenever a session
timeout occurs the user is redirected to the proper page but lacks
the anchor which tells our angular routing what to load. Since all of our
pages include the base route, this adds a check if the hash-path is empty
to inspect the full url, extract the current entity page and add that
to the hash-path. This assumes that the structure of our pages is
'/katello/entity#/entity'.