Aleem,
[ I've copied the list, because someone with more knowledge of the
internals may be able to answer this question better than I ]
I think this is the full request, but I might be mistaken. To verify
this, look at the code for mech->click() - you'll have to follow the
call as it assembles the request. Maybe I missed a relevant call, but I
thought that cookies were added somewhere in $mech->_modify_request( $r ).
If I've missed something, I'd be very happy if you can send me a patch ;-)
Cheers,
Peter
Aleem Mawji wrote:
Peter,
one hiccup is that i can't see the entire request. in other words, i can
see the posted form but i don't see the cookie data being sent. im
concerned that via all the javascript on the site i am working on,
certain cookies are being assigned values that mech would not have any
way of knowing and wanted to compare the complete post (form and cookies)
versus the complete post in http headers.
how can i view the full request (including all cookies and any other
headers)?
maybe a stupid question.
thanks again,
Aleem
-------------------------- Original Message ----------------------------
Subject: Re: preferred way to get request from perl mechanize
From: "Peter Stevens" <[EMAIL PROTECTED]>
Date: Sun, July 9, 2006 1:38 pm
To: "Aleem Mawji" <[EMAIL PROTECTED]>
-------------------------------------------------------------------------
Hi Aleem,
I just posted a solution to libwww (which seems to have gotten eaten in
the online archives, so I have reposted it with the
WWW::Mechanize::Debug package in the text of the message, which I also
copied to you. Hope it helps.
Cheers,
Peter
Aleem Mawji wrote:
Peter,
I am sorry to trouble you with my question. I noticed that you asked
on
a perl forum recently for the preferred way to get what is actually
requested from perl mechanize. I have the same question.
you also mentioned that you solved this problem by following the code
into the innards of HTTP::Request. I was wondering if you could help
me
do the same as i have not seen anything else posted anywhere on this
subject.
regards and thank you in advance,
Aleem
