Re: [Hampshire] Possibly daft Perl/DOS question

On 13/07/07, Vic <lug@???> wrote:
> > that has indeed put in CRLF pairs (looking at Wireshark). So
> > clearly I'm barking up the wrong tree as to the precise problem...
>
> That's usually the case with Internet servers - most of them are very
> permissive when it comes to LF or CRLF...
>
> The one notable exception I've found is MS Exchange. That gets very heated
> about it - to the extent that I've seen it reject messages that go through
> spamassassin (which is very untidy when it comes to preserving
> line-endings).

I Read In A Book [1] :
"The line termination for network communication should be \n\n.
However, because of the differences in line termination under
different platforms, care should be taken to ensure that this value is
actiually sent and received. You can do this by using the octal values
\012\012. Another alternative is to use the constants $CR,$LF, and
$CRLF ..."

- wonder if it might be worth running a few trials whilst watching
what's happening using tcpdump (or ethereal).

We did have an application once, Perl on both ends, one end being
WIndoze and the other Red Hat, where we had to set $/ and $\ both to
$LF$LF on each end to get it to work...

[1]M C Brown: "Perl The Complete Reference" , Osborne.

Other than that the only uploading I have done was from a web page
using CGI.pm's upload button, which was easy B-) , so can't really
help with the Content-Type statement.