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%5E48624024 but I am getting some forward slashes encoded like this.http://cit2.iam-secure.aaaaaaaa.com/bestbuy%2Ftransactions/online-transactions%2F20151020%5E960%5E960%5E48624024%7D How do I stop this?? Thank you.

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.

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!!

Not tried ever. But worth trying to put the value in a custom property and see that works.

The first part of the URL is indeed a custom property that is used in the Path: varialbe of the form builder. It is referenced like this. ${#Project#TransactionPath} and it is getting encoded in the actual URL call.Like this.bestbuy%2Ftransactions but this is not happening for all of my tests..

Did you try disabling encode URL? http://www.soapui.org/rest-testing/reference/method-window.html Although I rather suspect your URL is defined wrong. But withouth further information it is hard to tell.

If the value supplied in PATH/ TEMPLATE parameter is passed in the URL, then it is expected behavior that it gets encoded like this. I don't think SoapUI does different on this, http://cit2.iam-secure.aaaaaaaa.com/bestbuy%2Ftransactions/online-transactions%2F20151020%5E960%5E96... From the above URL, the RED highlighted items should be PATH parameter. If you edit in WADL/ WSDL to supply as different PATH parameters, I guess we can eradicate this problem. Thanks,Samy

How do I stop URL forward slash from being encoded?

18 Replies

nmrao
Champion Level 3
9 years ago
Not tried ever. But worth trying to put the value in a custom property and see that works.
- waynemmn
  Contributor
  9 years ago
  The first part of the URL is indeed a custom property that is used in the Path: varialbe of the form builder. It is referenced like this. ${#Project#TransactionPath} and it is getting encoded in the actual URL call.
  Like this.
  bestbuy%2Ftransactions
  
  but this is not happening for all of my tests..
  - SiKing
    Community Expert
    9 years ago
    Did you try disabling encode URL?
    
    http://www.soapui.org/rest-testing/reference/method-window.html
    
    Although I rather suspect your URL is defined wrong. But withouth further information it is hard to tell.
waynemmn
Contributor
9 years ago
I see on thing that is happening for this Request.

In the fom view, my path is defined like this.
${#Project#TransactionPath} with an actual value of this bestbuy/transactions.
If I define my entity like this:
online-transactions/abcd

Having it defined like this builds the URL like this.
http://cit2.iam-secure.bestbuy.com/bestbuy/transactions/online-transactions/abcd

but my last item "abcd" is a data item that is actually defined like this "20151019^960^960^40615329"

So when I enter a value like this into the entity field
then my URL become like this
http://cit2.iam-secure.bestbuy.com/bestbuy%2Ftransactions/online-transactions%2F20151019%5E960%5E960%5E40615329

When I go ahead and encode my query value like this: 20151019%5E960%5E960%5E40615329

Then the one slash in my path still get encoded.
http://cit2.iam-secure.bestbuy.com/bestbuy%2Ftransactions/online-transactions/20151019%5E960%5E960%5E40615329

:(

I can't seem to turn off encoding!!
waynemmn
Contributor
9 years ago
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??
- GillerM
  Staff
  9 years ago
  Yes. Just encode the part of the URL with the TEMPLATE parameter - http://readyapi.smartbear.com/structure/parameters/template
  
  Then the slash would be around the TEMPLATE param and will not be encoded
  - 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????

Forum Discussion

How do I stop URL forward slash from being encoded?

18 Replies

Related Content

Encoding

VBScript forward directive

Transfer-encoding: chunked

Authorization Tag For Basic BASE64 Encoding

RestAPI for Base64 Encoder

Recent Discussions

MQTT Receive Creates Own Topics

MQTT Publish Step Ignores Client ID

Mismatch between response from a CURL request and ReadyAPI response

Reading dynamic parameter from resource path

Parameterising JDBC Connection Settings..Can you do it?