Should Accept Text/Xml: multipart/related be Accept: ...? See RFC 2616. IIRC, header names are not supposed to have spaces in them (check my memory, please).

What reason are you looking to disable some of the features that LWP is able to support under the hood? Is the server unable to handle those? Or are these changes trying to 'fix' some other symptom that you are seeing.

If you do need to remove these headers, fine, but with my question on the Accept header, I am wondering if this might be a bug hunt with the wrong target.

--MidLifeXis

In reply to Re: "Bad" http headers in LWP::UserAgent by MidLifeXis
in thread "Bad" http headers in LWP::UserAgent by adamm

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.