Forum Discussion

s_martin_253133's avatar
s_martin_253133
Icon for Nimbostratus rankNimbostratus
Mar 07, 2016

Losing full URL during multi-domain auth

We have a "dynamic" VS setup which will first redirect incoming https connections to a central portal page for authentication at which point the portal uses an irule to redirect back to the original "dynamic" VS and an irule then passes authenticated users into the appropriate back-end pool. The process works like a champ when a simple host.domain.com needs to be requested, however the process does not function when additional URL params are passed. From what I can tell from a fiddler trace I am losing my full path during the initial 302 redirect to the central portal page (Primary Authentication URI). Any way to preserve this information through redirects?

 

REQUESTED

 

 

RETURNED AFTER AUTHENTICATION (via Primary Authentication URI)

 

 

Any assistance would be much appreciated.

 

Thanks,

 

Steve

 

application delivery
BIG-IP Access Policy Manager (APM)
LTM

1 Reply

  • Kai_Wilke's avatar
    Kai_Wilke
    Icon for MVP rankMVP
    Mar 07, 2016

    Hi Steve,

    The portion after the

    (hash-sign) is called an "URL-Fragment" which is used by your browser to select or scroll down to a specific section of the requested page. The "URL-Fragment" is NEVER send by your browser to the F5 and thats why the redirect is not including the trailing URI portion...

    For more information refer to: https://en.wikipedia.org/wiki/Fragment_identifierBasics

    There is unfortunately no easy fix for your specific issue. It would more or less require a decent change to your web application to keep the trailing part while redirecting back and forth to the login page.

    Note: Sorry for being the guy telling you bad news... 😞

    Cheers, Kai