[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: RE: [wsrp-interop] Spaces in resource URLs revisited.
You are correct. Apparently, there is URL parameter
encoding and URL path encoding (at least in .NET). Path encoding is used
to encode special characters in the path not the parameters and so a space that
is path encoded is “%20” where as when parameter encoded, it is “+”.
The portlet is now updated and deployed
with correct semantics (hopefully). In the Resource Download portlet the
URL display is a properly path encoded URL. However, when it is used as
part of the WSRP resource URL, the whole of it is parameter encoded. Pseudo code for setting the URL property/attribute
of a WSRP Resource URL would be: WsrpUrl.Url =
UrlParameterEncode(UrlPathEncode(rawUrl)) Please let me know if any of the above is
incorrect or if it is just applicable to .NET. Nader From: Nathan Lipke [mailto:nlipke@bea.com] I'm doing some interop testing with
NetUnity with a proxied URL with a space. It appears some servers (Weblogic,
and IIS) do not support the '+' for a space in a resource. In this case the %20
must be used. Can we issue a clarification note that that either form can be
used, depending on what resource server supports? 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]