problems handling chr(13) chr(10) as raw data

From: MikeS <mike.sztanko_at_stroud.gov.uk>
Date: 20 Oct 2005 09:30:34 -0700
Message-ID: <1129825834.358992.5880@f14g2000cwb.googlegroups.com>

I've been trying to encode strings of the form

"A \r\n\r\n" as base64 using utl_encode.base64_encode

At the other end the decode just gets "A \n \n"

Checked the encoded output and sure enough it's ignoring the \r's. Encoded and wrote encoded output to file and only has 4 characters QQoK which corresponds to "A \n \n".

Does anyone know why this is. Checked with utl_raw, length and substr functions and it treats this combinition as 3 chars. Is the encoding doing something similar. Received on Thu Oct 20 2005 - 11:30:34 CDT