RE: [wsrp-wsia] [change request #129] wsrp-url portlet URL parame ter

[Rich Thompson <richt2@us.ibm.com>]

Based on our resolution to #129, I reworded this area as:

This parameter provides the actual URL to the resource. Note that this 
needs to be an absolute URL as the resource fetch 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. Consumers are encouraged 
to use the same communication style (e.g. HTTP Get or Post) for retrieving 
the resource as was used in requesting the resource by the user-agent.

Rich Thompson




"Kropp, Alan" <Alan.Kropp@vignette.com>
02/24/2003 07:46 PM
 
        To:     wsrp-wsia@lists.oasis-open.org
        cc: 
        Subject:        RE: [wsrp-wsia] [change request #129] wsrp-url 
portlet URL parame      ter


At the last issues call, we discussed whether it was necessary to mandate
the Consumer use a  specific request style when "proxying" a resource.  I
think the proposed wording below was considered too restrictive, so let me
offer another re-wording that hopefully is less so:

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 a request 
style (e.g. HTTP GET or POST) that is appropriate to the target resource.
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.

-----Original Message-----
From: Rich Thompson [mailto:richt2@us.ibm.com]
Sent: Friday, February 07, 2003 7:03 AM
To: wsrp-wsia@lists.oasis-open.org
Subject: [wsrp-wsia] [change request #129] wsrp-url portlet URL
parameter


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.

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>

----------------------------------------------------------------
To subscribe or unsubscribe from this elist use the subscription
manager: <http://lists.oasis-open.org/ob/adm.pl>