Forum Stats

  • 3,814,410 Users
  • 2,258,870 Discussions
  • 7,892,703 Comments

Discussions

Is there a way to disable URL Encoding on a REST request

Tom Gehrke
Tom Gehrke Member Posts: 1 Green Ribbon
edited Jan 5, 2022 4:54PM in SOA Suite Discusssions

Background:

We are using SOA to "front-end" PeopleSoft's QAS_EXECUTEQRY_REST_GET service operation. At it's simplest, we simply want to pass through an incoming operation (GET).

Problem:

The service operation requires passing multiple fields. It does this by overloading single parameters. So instead of sending...

bind1=value1&bind2=value2&bind3=value3

...the service operation is expecting...

prompt_uniquepromptname=bind1,bind2,bind3&prompt_fieldvalue=value1,value2,value3

The issue is that the payload is being urlencoded. So what the service operation sees is...

prompt_uniquepromptname=bind1%2Cbind2%2Cbind3&prompt_fieldvalue=value1%2Cvalue2%2Cvalue3

Because the endpoint is not url decoding, it translates this into a single field "bind1%2Cbind2%2Cbind3" and a single value "value1%2Cvalue2%2Cvalue3" which, of course, does not exist.

Question(s):

Is it possible on the SOA side of this, to disable url encoding for a request/parameter?

I have a decent amount of experience with web services, but am pretty new when it comes to Oracle, SOA and service operations. I fear I may be missing something obvious.

Thanks!

Tagged: