axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Fred Preston (JIRA)" <>
Subject [jira] Closed: (AXISCPP-777) Monitor program does not handle lone LF's correctly when the Unit Test message is chunked.
Date Wed, 05 Apr 2006 12:14:08 GMT
     [ ]
Fred Preston closed AXISCPP-777:

> Monitor program does not handle lone LF's correctly when the Unit Test message is chunked.
> ------------------------------------------------------------------------------------------
>          Key: AXISCPP-777
>          URL:
>      Project: Axis-C++
>         Type: Bug

>  Environment: n/a
>     Reporter: Fred Preston
>     Assignee: Fred Preston
>     Priority: Minor

> The HTTP header and chunk sizes need to be delimited with CR LF's.  The 'server response'
expected files used to mimic the response of a server when performing unit tests also need
to have the correct delimiting character combinations in the fake response messages (generated
by the monitor).  Problems arise because the expected response files have been captured on
different operating systems (Unix and Windows) and then edited using a variety of editors
that interpret the CR character differently.  Thus the file may be stored with or without
the CR characters.  Also, CMVC can be set to convert a single LF character into a CR LF combination.
 The outcome of all this character manipulation is that LF's may or may not have the necessary
associated CR for it to be recognised by the HTTP transport.  It is not just sufficient to
look for every LF and to prefix it with a CR because the context of that LF must be taken
into consideration.  For example, if a LF is found in the HTTP header then it definitely needs
a CR prefix.  This also applies when the message is chunked and the chunk size must also be
delimited by the CR LF sequence.  But, when a LF appears inside a chunk of data it should
remain unchanged unless the chunk size is different from the actual data size between chunks,
in which case the CR has probably been stripped out and needs to be replaced.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
For more information on JIRA, see:

View raw message