ws-soap-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject RE: Extra line appearing in Apache Response
Date Mon, 30 Sep 2002 03:46:47 GMT
I beleive this is not a a Apache SOAP bug. White space and
lines between tags should not matter in XML parsing. Please
refer to XML specification as shown below:

2.10 White Space Handling

In editing XML documents, it is often convenient to use "white space"
(spaces, tabs, and blank lines, denoted by the nonterminal S in this
specification) to set apart the markup for greater readability. Such white
space is typically not intended for inclusion in the delivered version of
the document. On the other hand, "significant" white space that should be
preserved in the delivered version is common, for example in poetry and
source code.

2.11 End-of-Line Handling

This is a flaw in client, IMHO. It will be "nice"
on part of Apache SOAP to avoid that empty line but it is
NOT a requirement.

On a related note, I am surprised and apalled by this kind of
" SOAP interop" problems. SOAP/XML has been there for quite
some time and still some commercial stacks has such trivial issues.

Soumen Sarkar.

-----Original Message-----
From: Damian Alonso
To: ''
Sent: 9/29/2002 7:38 PM
Subject: Extra line appearing in Apache Response

I'm wondering if anyone has seen this problem before. 

We currently have an Apache SOAP 2.2 Service running, which is returning
a http response that looks like this: 

<> ">


The problem we have found is that some clients (e.g SilkPerformer for
.NET) are having problems handling the extra carriage return between the
'response' closing tag and the 'body' closing tag.  On all the examples
I have looked at, there normally is no carriage return between the
'response' closing tag and the 'body' closing tag.  

<> ">

We have found that this extra carriage return is in all our Apache SOAP
responses (no matter what service we are offering).  My question's are:

- Is that allowed (i.e the extra carriage return) as part of the SOAP
1.1 specification?? 
- Is that a bug with Apache's way of encoding the response?? 
- Does anyone know why this extra carriage return is being inserted
(i.e what part of the Apache SOAP code does this serialization of the

- Is it a flaw in the client because it cannot handle the extra carriage

Any information on this or similar problems would be greatly

Thanks in advance, 


View raw message