Re: URI help

[Michael Engelhart <me...@navigatus.com>]

Just to get this into the mail archives in case anyone else runs into this
issue, I downloaded the Xalan source code and edited
org.apache.xml.utils.URI.java and changed:

  private static final String MARK_CHARACTERS = "-_.!~*'() ";


To 

  private static final String MARK_CHARACTERS = "-_.!~*'() <>";


And rebuilt with ant.  This obviously isn't the best solution because it's
messing with the RFC (sort of - the RFC is a bit vague by calling the use of
<> 'unsafe'??) but for this situation it solved the problem of passing XML
as a GET parameter when using the document() function call.

Thanks for everyone's suggestions...

Mike

On 5/31/02 2:16 PM, "Denis Haskin" <De...@HaskinFerguson.net> wrote:

> In my opinion, if this upstream provider doesn't accept the encoded URL as you
> gave it, it's their system that's broken.   As you mentioned, the spec clearly
> says that "<" and ">" and not considered safe in URLs and should be encoded,
> and
> their application should handle that.
> 
> dwh
> 
> 
> Michael Engelhart wrote:
> 
>> Thanks - that gets the URL encoded for Xalan.  But the problem is that I
>> then have something similar to this:
>> http:/the.company.com/xmlInterface.jsp?xml=%3C
>> Request%3E%3Cvar1%3E164881%3C%2Fvar1%3E%3C
>> 
>>  and the  response back from their system is that the XML is not
>> well-formed...
> 
>