Skip Menu |

This queue is for tickets about the WWW-Mechanize-Chrome CPAN distribution.

Report information
The Basics
Id: 127738
Status: resolved
Priority: 0/
Queue: WWW-Mechanize-Chrome

People
Owner: Nobody in particular
Requestors: enrique.pessoa [...] dfinsolutions.com
Cc:
AdminCc:

Bug Information
Severity: (no value)
Broken in: (no value)
Fixed in: 0.25



Subject:
Date: Mon, 19 Nov 2018 14:33:59 -0200
To: bug-WWW-Mechanize-Chrome [...] rt.cpan.org
From: Enrique Pessoa <enrique.pessoa [...] dfinsolutions.com>
Dear Corion and WWW-Mechanize-Chrome maintainers, I found the setRequestInterception method was not working due to two simple mistypes. You can find the unified diff file attached. Thank you for your work on this module, Enrique

Message body is not shown because sender requested not to inline it.

Subject: Re: [rt.cpan.org #127738]
Date: Mon, 19 Nov 2018 22:05:33 +0100
To: bug-WWW-Mechanize-Chrome [...] rt.cpan.org
From: Max Maischein <corion [...] corion.net>
Hello Enrique, Show quoted text
> I found the setRequestInterception method was not working due to two simple > mistypes. > > You can find the unified diff file attached. >
thank you very much for spotting, reporting and patching this issue! I have released 0.24 with your fix. Please tell me if that fixes the issue for you! -max
Subject: Re: [rt.cpan.org #127738]
Date: Wed, 21 Nov 2018 12:11:01 -0200
To: bug-WWW-Mechanize-Chrome [...] rt.cpan.org
From: Enrique Pessoa <enrique.pessoa [...] dfinsolutions.com>
Hi Max, It was a pleasure to contribute. Yes, it's there. Thanks for integrating it so quickly. I found setRequestInterception notifies there has been a response for the given request but, unfortunately, it does not allow us to access the response contents. We're now looking for other alternatives. On Mon, Nov 19, 2018 at 7:05 PM Max Maischein via RT < bug-WWW-Mechanize-Chrome@rt.cpan.org> wrote: Show quoted text
> <URL: https://rt.cpan.org/Ticket/Display.html?id=127738 > > > Hello Enrique, >
> > I found the setRequestInterception method was not working due to two
> simple
> > mistypes. > > > > You can find the unified diff file attached. > >
> thank you very much for spotting, reporting and patching this issue! I > have released 0.24 with your fix. Please tell me if that fixes the issue > for you! > > -max > >
Thank you for reporting this issue. The method call is now fixed. As to getting at a response body, you maybe have to fetch the body using ->getResponseBody?