Forum Discussion

waynemmn's avatar
waynemmn
Contributor
9 years ago
Solved

How do I stop URL forward slash from being encoded?

I am creating some new tests calling a new rest end point.   I need to call the endpoint like this. http://cit2.iam-secure.aaaaaa.com/bestbuy/transactions/online-transactions/20151020%5E960%5E960%...
  • SiKing's avatar
    SiKing
    9 years ago

    Your parameter "entity" has a slash in it! You are either going to get the whole parameter encoded or nothing.

    You need to break this up into two parameters, maybe: "entitypre" and "entitypost", or something. The separating slash between parameters will not be encoded, but the two _parts_ will.

waynemmn's avatar
waynemmn
Contributor

No resolution on this yet.

Does anyone have any help or insight?

 

Is there a way to encode just the data part of the url so that it does not force encoding the rest of the url??

 

 

 

  • waynemmn's avatar
    waynemmn
    Contributor
    9 years ago

    I am already using a template for both the Path Section of the URL and the Entitiy Portion. 

    See attached image. 

    If the data portion of the URL has the character "^" in the data. like this. 

    20151103^960^960^104521

    Then the Path part and the entity part get encoded. 

    http://cit2.iam-secure.bestbuy.com/bestbuy%2Ftransactions/online-transactions%2F20151103%5E960%5E960%5E102658

     

    If I replace the "^" with an "_"then nothing gets encoded. 

    http://cit2.iam-secure.bestbuy.com/bestbuy/transactions/online-transactions/20151103_960_960_104521 

     

    I am not sure how you think using templates will stop this????

     

     

     

     

     

    • SiKing's avatar
      SiKing
      Community Expert
      9 years ago

      Your parameter "entity" has a slash in it! You are either going to get the whole parameter encoded or nothing.

      You need to break this up into two parameters, maybe: "entitypre" and "entitypost", or something. The separating slash between parameters will not be encoded, but the two _parts_ will.

      • waynemmn's avatar
        waynemmn
        Contributor
        9 years ago

        ok ok,

        Your answer got me thinking and I finally was able to resolve this. 

         

        I broke the URL up into 4 seperate Parameters so there was no slash (/) in any value and then I placed the final data portion of the URL (20151103^960^960^103694) in it's own parameter. 

         

        Only that final portion got encoded and that is what this query needed. 

         

        Thanks everyone for your help!!