[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsrp-interop] wsrp-extension value encoding clarification
I got this value instead: param1%3dvalue1%26param1%3dvalue2%26param%253d2%3dthis%2b%2526%2bthat I used this code in .NET: string x = HttpUtility.UrlEncode("param1") +
"=" + HttpUtility.UrlEncode("value1"); x += "&" +
HttpUtility.UrlEncode("param1") + "=" +
HttpUtility.UrlEncode("value2"); x += "&" + HttpUtility.UrlEncode("param=2")
+ "=" + HttpUtility.UrlEncode("this & that"); Console.WriteLine(HttpUtility.UrlEncode(x)); Nader From: Nathan Lipke
[mailto:nathan.lipke@oracle.com] I was reading the wsrp-extensions part of the
spec: 9.2.1.9 and I am assuming parameter names and values should be
encoded. Here's the relevant section: 9.2.1.9 wsrp-extensions Extensions to the data supplied on the
URL which this protocol defines MUST use the following sequence to encode the
additional information into the wsrp-extensions portlet
URL parameter:
"param1=value1¶m1=value2¶m2=value3
param1%3Dvalue1%26param1%3Dvalue2%26param2%3Dvalue3
So for example if param1=value1 were more
complex:
I would expect the resulting string to be:
Is this correct? Thanks, Nate |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]