Document: Spec Section: 10.2.1.1.4.1 Page/Line: 58/29-33 Requested by: Alan Kropp Old text:

wsrp-url This parameter provides the actual URL to the resource. Note that this needs to be an absolute URL as the resource fetch will likely use HTTP GET and it will have no base for use in fetching a relative URL. Also note that since this URL will appear as a parameter value, it MUST be strictly encoded (i.e. "&", "=", "/", and "?" need to be url-escaped) so that special URL characters do not invalidate the processing of the enclosing URL.

Proposed text:

wsrp-url This parameter provides the actual URL to the resource. Note that this needs to be an absolute URL as it will have no base for use in fetching a relative URL. When the Consumer receives the client's request for the resource, it MUST propagate the request to the resource using the request style (e.g. HTTP GET or POST) specified by the client. Also note that since this URL will appear as a parameter value, it MUST be strictly encoded (i.e. "&", "=", "/", and "?" need to be url-escaped) so that special URL characters do not invalidate the processing of the enclosing URL.

Reasoning: It wasn't clear that when proxying an url to a resource, that the Consumer needs to use the request style that was originally encoded in the portlet's markup. Without the change, the spec seems to indicate that Consumer's only proxy GET-style requests.