axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yampolsky, Robert" <>
Subject RE: URL encoding or HTML encoding
Date Thu, 26 May 2005 17:59:47 GMT
It looks like the HTML encoding's right (as far as I know).  The bit
about URL encoding was a red herring.  The guy thought HTML encoding was
called URL encoding.  He's talking about the same thing I am (&lt; ,
etc), so I think it's not an issue.


-----Original Message-----
From: Samisa Abeysinghe [] 
Sent: Thursday, May 26, 2005 5:23 AM
To: Apache AXIS C User List
Subject: Re: URL encoding or HTML encoding

Going though the code in line with your description, it looks to me that
Axis C++ is using HTML encoding and it does not have support for URL

However, I am not sure if HTML encoding is done properly - I do not
think we have a test to verify this. If you could lead to some test data
(that is input and expected output) we would be able to verify.


On Wed, 2005-05-25 at 21:16, Yampolsky, Robert wrote:
> I'm trying to figure out whether Axiscpp uses URL encoding or HTML
> encoding to handle special characters in message payloads.
> I'm guessing it uses HTML encoding, since I see references to
> ENCODED_LESSER set to "&lt;".  But the organization that's setting
> standards for my web services project just put out a survey saying
> they think 'everyone' uses URL encoding (which a quick Google search
> shows to be %<hex>).  Since these guys seem to have embraced .NET, I
> want to make sure they're not just saying .NET uses URL encoding, so
> everyone must...
> Can Axiscpp do it either way, or does it always use HTML encoding (or
> something else)?
> Thanks,
> R o b   Y a m p o l s k y
> Harris Corporation
> (212) 303 - 4250
Samisa Abeysinghe <>
Virtusa Corporation

View raw message