in reply to Re^2: HTTP Headers Using WWW::Mechanize
in thread HTTP Headers Using WWW::Mechanize

Patches welcome. If something's unclear, please send me updates to the doc that expand on it. It's hard for me, as the author, to know what people need to know, or if it's not as clear as should be.

xoxo,
Andy

  • Comment on Re^3: HTTP Headers Using WWW::Mechanize

Replies are listed 'Best First'.
Re^4: HTTP Headers Using WWW::Mechanize
by Limbic~Region (Chancellor) on Feb 01, 2005 at 14:19 UTC
    petdance,
    It isn't specifically that something is unclear. It is that WWW::Mechanize is built on a lot of prior art.

    There isn't a succintly way to say that WWW::Mechanize is a subclass of LWP::UserAgent which uses HTTP::Response which is a subclass of HTTP::Message which uses HTTP::Headers so while there isn't a direct method of listing the header keys or there values, you can still get to them.

    Even if that could be said concisely, it would only address the headers issue. The underlying issue is that to get the absolute most out of a module like WWW::Mechanize, the user needs to spend some time understanding the prior art and how it is being used. As such, my patch is just an addition to the FAQ. While I have emailed it to you, I am including a copy here as well.

    Read more... (1213 Bytes)

    Cheers - L~R

[reply]
[d/l]
Re^4: HTTP Headers Using WWW::Mechanize
by igoryonya (Pilgrim) on Oct 15, 2022 at 01:11 UTC
    So, nobody has done the patch to the documentation still.
    I've had struggle with the same thing and didn't know, how to get the headers, until i got to this post, because the documentation doesn't mention anything about it.
[reply]

      You're replying to a 17 year old post, I don't see your pull request or issue to request this.

[reply]
        Exactly, the issue hasn't been fixed for 17 years.
        I don't know, how to do "pull requests".
[reply]

In Section Cool Uses for Perl