[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Producer URL writing question
I have a question on URL-encoding needs of URL tokens during token replacement in URLs. Let's say, a consumer sends a URL template of the following form: http://foo.com/blah/blah?src={wsrp-url}&rw={wsrp-requiresRewrite} The producer wants to substitute "http://bar.com/bar.gif" for wsrp-url token, and "false" for wsrp-requiresRewrite, and so the resulting URL would look like http://foo.com/blah/blah?src=http://bar.com/bar.gif&rw=false Since this URL is not valid, the producer will have to URL encode the wsrp-url value, and the resulting URL will be http://foo.com/blah/blah?src=http%3A%2F%2Fbar.com%2Fbar.gif&rw=false However, the producer has no knowledge of whether (a) such encoding is required, and (b) such encoding would result in the resource being fetched correctly. For example, consider the following URL template. {wsrp-url}?rw=wsrp-requiresRewrite In this case, if the producer decides to URL-encode wsrp-url value before substitution, just like it did above, it would result in a URL like http%3A%2F%2Fbar.com%2Fbar.gif?rw=false and the browser would fail to fetch the resource. I presume similar issues occur with other parameters when URL templates are JavaScript based. How should the producer determine when to URL-encode parameters? Regards, Subbu _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]