Need to have agent correctly encode/decode hashtag in URL

Idea created by SamatBoA on Jul 22, 2016
    Not planned
    Score4
    • SamatBoA
    • CBertagnolli
    • Josh Perlmutter
    • Subhadra.kaja


    We have an application that contains the hashtag character in the URL:

     

    http://our-site/path1/path2/#/path3/destination

     

    when redirected to the login page, the browser is correctly handling the hashtag but when the agent sends the user back to the target, it does not decode it so the URL becomes invalid.

     

    We opened a support case and was told that hashtag was not in the list of special characters that the agent could handle and that an enhancement request was necessary.

     

    Our immediate need is for web agent 12.51 cr7 enhancement.