interesting queryparam issue

Not applicable

we are seeing some bizarre behavior w/in the assign message policy and are curious if this is designed as expected:

I looking to add a query parameter with no value with the Assign Message policy:

<Add>
  <Headers/>
    <QueryParams> 
      <QueryParam name="format">json</QueryParam> 
      <QueryParam name="with-data"></QueryParam> 
    </QueryParams>
  <FormParams/>
</Add>

I’m expecting to get:

/something/otherthing/somepath?op=search&format=json&with-data

But im getting:

/something/otherthing/somepath?op=search&format=json&with-data=

Is this possible to do w/o dropping into Javascript?

0 1 108
1 REPLY 1

Hi Benjamin,

There isn't a way to do this with an AssignMessage policy. Whilst not guaranteed - many backends will treat ...

?withdata

and

?withdata=

... exactly the same.

Thanks, Sean