Passing % OR # in URL is not working in 716 version. It was working in 533.

http://servname/ibi_apps/WFServlet?&IBIF_ex=test&PARM1=ALL&PARM2=%&PARM3=TEST1

The above url is not working in 716 version. Anybody face this issue.

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:

CHAR     ESC
------   ----
SPACE    %20
#        %23
$        %24
%        %25
&        %26
/        %2F
:        %3A
;        %3B
<        %3C
=        %3D
>        %3E
?        %3F
@        %40
[        %5B
\        %5C
]        %5D
^        %5E
`        %60
{        %7B
|        %7C
}        %7D
~        %7E

Hope this helps....

quote:

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

http://servname/ibi_apps/WFServlet?&IBIF_ex=test&PARM1=...ARM2=%25&PARM3=TEST1

The problem is there are lot of programs we have like this and if we have to change the code then we need to touch all those.

I am trying to check for some settings to do this. Because I dont want to ask the other developer to change all the reports.

Here's an interesting read: Blooberry: URL Encoding

% and # are considered "Unsafe characters" versus "Reserved characters" but should also be encoded.

quote:

% 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:

A-Z a-z 0-9 - . _ ~

Percent Encoding