As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
Kamesh, For whatever reason this indeed does not work anymore in 716 (or 717). It still worked ok in 713, so somehwere between these two releases this must have changed. The way to do this is to escape these special characters, for the % sign you should now use %25, for the # sign you should use %23. Below a complete list of escape codes for special characters:
Passing % OR # in URL is not working in 716 version. It was working in 533.
It really should of never worked as URL Encoding uses the % and # characters to mean certain things. (% is used to encode / escape other chacters and # is used to indicate an identifer / anchor within the page).
If you want to pass the % character use %25 and for the # character use %23
% and # are considered "Unsafe characters" versus "Reserved characters" but should also be encoded.
That is followed on by that authors WHY of
quote:
Some characters present the possibility of being misunderstood within URLs for various reasons. These characters should also always be encoded.
This is a case of a web author not quite choosing the correct word and maybe not fully understanding the RFC.
RFC 3986 (01/2005)states that the "Reserved Characters" are a combination of general deliminators and sub deliminators. That set of characters as defined in the RFC are:
! * ' ( ) ; : @ & = + $ , / ? % # [ ]
The RFC further goes on and defines characters that are allowed but do not have a reserved purpose are called unreserved. That set of characters as defined in the RFC would be: