[asterisk-bugs] [Asterisk 0018186]: Malformed XML response

[Asterisk Bug Tracker]

A NOTE has been added to this issue. 
====================================================================== 
https://issues.asterisk.org/view.php?id=18186 
====================================================================== 
Reported By:                nivaldomjunior
Assigned To:                
====================================================================== 
Project:                    Asterisk
Issue ID:                   18186
Category:                   Core/ManagerInterface
Reproducibility:            always
Severity:                   trivial
Priority:                   normal
Status:                     new
Asterisk Version:           1.8.0 
JIRA:                        
Regression:                 No 
Reviewboard Link:            
SVN Branch (only for SVN checkouts, not tarball releases): 1.8 
SVN Revision (number only!):  
Request Review:              
====================================================================== 
Date Submitted:             2010-10-22 07:53 CDT
Last Modified:              2010-10-27 12:12 CDT
====================================================================== 
Summary:                    Malformed XML response
Description: 
Using the AJAM and XML to access the manager interface we receive a
malformed XML response.
We tested using a java and a php application, and both had received the
ajax response with error. The final tag </ajax-response> is not there.

We tested using the browser and the results are:

Chrome - Didn't worked. No </ajax-response> tag:
<ajax-response> 
<response type='object' id='unknown'><generic response='Success'
message='Authentication accepted' /></response> 

Safari - Didn't worked. The </ajax-response> tag is there, but is not
complete. The > is not there:
<ajax-response>
<response type='object' id='unknown'><generic response='Success'
message='Authentication accepted' /></response>
</ajax-response

Firefox - Worked. The XML response is complete:

?
<ajax-response>
?
<response type="object" id="unknown">
<generic response="Success" message="Queue summary will follow"/>
</response>
?
<response type="object" id="unknown">
<generic event="QueueSummary" queue="Fila-Unimed" loggedin="0"
available="0" callers="0" holdtime="0" talktime="0" longestholdtime="0"/>
</response>
?
<response type="object" id="unknown">
<generic event="QueueSummary" queue="fila-unimed-nne" loggedin="0"
available="0" callers="0" holdtime="0" talktime="0" longestholdtime="0"/>
</response>
?
<response type="object" id="unknown">
<generic event="QueueSummaryComplete"/>
</response>
</ajax-response>


====================================================================== 

---------------------------------------------------------------------- 
 (0128419) davidw (reporter) - 2010-10-27 12:12
 https://issues.asterisk.org/view.php?id=18186#c128419 
---------------------------------------------------------------------- 
The only obvious difference is that there is a bogus empty line at the
start of the XML payload in 1.8.  I'm not sure if XML allows that or not. 
I don't think the fact that the real start of payload is in a different
fragment from the end of the header is relevant.

As an incidental observation, this is showing severe IP fragmentation
because of a very short MTU (https://issues.asterisk.org/view.php?id=136#c500
bytes) and no use of Path MTU discovery. 
Efficient operation with this requires that you explicity set MTU in the
routing tables, or on the interface. 

Issue History 
Date Modified    Username       Field                    Change               
====================================================================== 
2010-10-27 12:12 davidw         Note Added: 0128419                          
======================================================================