I've seen oddball behavior with POST once before: a client, who I won't mention, had a not-so-great firewall configured and managed by another vendor. The client was trying to post replies to questions on a message board on their website (which was hosted by the company I was working for at the time), but the replies kept getting cut off at 5K. It turns out the firewall itself was truncating the POST requests.... So it wouldn't surprise me one bit if a badly behaving proxy server were converting POSTs to GETs -- especially if it were a proxy designed to cache requests (since you can more readily cache the response to a GET than the response to a POST).

Spud Zeppelin * spud@spudzeppelin.com

In reply to RE: (Ovid) Re: 414 Request-URI Too Large by spudzeppelin
in thread 414 Request-URI Too Large by damian

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.