URI redirect - alternative to hash sign #config parameter in URL

Install & Config
1

We have a custom auth flow prior to Jitsi web that performs a redirect and stores the initial landing uri.

The problem is that everything after #(hash) is not lost in the redirect meaning we cannot do any URL parameter config to the jitsi UI at the moment.

Are there any other methods to configure the Jitsi UI without the #-sign?

Found this info in RFC 3986

RFC 3986 statement on fragments:

the fragment identifier is not used in the scheme-specific
processing of a URI; instead, the fragment identifier is separated
from the rest of the URI prior to a dereference, and thus the
identifying information within the fragment itself is dereferenced
solely by the user agent, regardless of the URI scheme. Although
this separate handling is often perceived to be a loss of
information, particularly for accurate redirection of references as
resources move over time, it also serves to prevent information
providers from denying reference authors the right to refer to
information within a resource selectively.

2

I use the following to keep fragments while redirecting:

1 Like
3

Thanks @emrah, interesting!

Trying to understand the flow here, how do you keep the fragement identifier so that the server sees it? To my understanding it is only visible on the client side?

4

That 's right. Therefore there is an internal redirection (rewrite line) in Nginx. The client goes to oidc-redirect.html transparently and the state doesn’t change on the client side. So, oidc-redirect.html can get the original URL with its querystring and fragment.

Then it redirects the client by keeping all these data.

2 Likes