Let's see now... certain amount of guesswork in places, but for what it's worth...

First, it's not an error message as such, it's a normal http response. It says at the start that it's HTTP/1.1, so let's have a look at the RFC... Looks like RFC 2616, Hypertext Transfer Protocol -- HTTP/1.1 is the one you want.

Next bit of the response: 302 Found. This is covered in section 10.3.2 of the RFC, and a bit higher up it explains that all the 3xx codes are to do with redirection. 302 found means that The requested resource resides temporarily under a different URI.

Now The temporary URI SHOULD be given by the Location field in the response. So it looks like this is a redirection from your original request, /controlcenter/, to /controlcenter/?u=100000&p=0x1000000000000 - interesting(ish).

(The bit you were worried about, Cache-Control: no-cache, must-revalidate, just indicates that this response shouldn't be cached).

Now LWP can, afair, follow redirections for you if you tell it to, but it can't in this case even if you *do* tell it to, because If the 302 status code is received in response to a request other than GET or HEAD, the user agent MUST NOT automatically redirect the request unless it can be confirmed by the user, since this might change the conditions under which the request was issued. - and our request was, of course, a POST, so the LWP module "MUST NOT" (this is RFC-language for "really really shouldn't, we mean it") follow the redirection automatically.

So what could you do?

I've been into this point-by-point not out of any intention to be patronising, but to assist those monks who might not have come across the RFCs before - they can be v.useful.

hth, andy.


In reply to HTTP/1.1 302 Found Re: Posting Form with LWP Produces 'no-cache, must revalidate' Error by andye
in thread Posting Form with LWP Produces 'no-cache, must revalidate' Error by sierrathedog04

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.