You might check your webserver's error logs, and see if there's any additional details in there.

For the CRLF issue, it's probably best not to use '\r\n', as '\n' is handled differently based on the OS you're using. I typically use "\015\012" for CRLF. (see perlport, 'Newlines' for details)

If that doesn't work, and you don't have access to the error logs to see what specific part of processing is throwing the error, I'd make sure that the request validates as XML, and against whatever schema you might have. (if that trailing semicolon is part of the message being sent, I'd suggest removing it).

In reply to Re: HTTP/1.1 400 Bad Request by jhourcle
in thread HTTP/1.1 400 Bad Request by Sham

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.