Your message dated Sun, 10 Jan 2016 15:34:20 +0100
with message-id <20160110153420.474f9fdae45f3ec6ac0bb...@paranoici.org>
and subject line Re: Bug#810005: xul-ext-cookie-monster: [regression] cannot 
login on www.amazon.com, even after temporarily allowing all cookies
has caused the Debian Bug report #810005,
regarding xul-ext-cookie-monster: [regression] cannot login on www.amazon.com, 
even after temporarily allowing all cookies
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)


-- 
810005: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=810005
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: xul-ext-cookie-monster
Version: 1.2.5-1
Severity: important

Hello!

I noticed a regression, after the recent

  [UPGRADE] iceweasel:amd64 38.5.0esr-1 -> 43.0.2-1
  [UPGRADE] iceweasel:amd64 43.0.2-1 -> 43.0.2-1+b1

I can no longer login on www.amazon.it or www.amazon.com, even after
temporarily allowing all cookies.
It used to work correctly before the above-mentioned upgrade (it just
needed the amazon.com or amazon.it cookies to be temporarily allowed).

Now, I access https://www.amazon.com and click on the Cookie Monster
button: I enable "Temporarily Allow Cookies from amazon.com" and
"Third Party Cookies → Temporarily Allow All" (please note that the
latter was previously superfluous). After doing that (with JavaScript
temporarily enabled by the No Script extension), I click on the
"Sign in" button of the amazon.com web site and I reach the sign in
page where a big warning says:

   .
  /!\   Please Enable Cookies to Continue
  --- 
        about cookies and how to enable them.


If I enter my e-mail address and password, I reach a page that says

  Please Enable Cookies to Continue
  
  To continue shopping at Amazon.com, please enable cookies in
  your Web browser. Learn more about cookies and how to enable
  them.
  
  Once you have enabled cookies in your browser, please click on
  the button below to return to the previous page.

  [ Go back to previous page ]


and I cannot actually access my amazon account.


I cannot understand what's going on.
Could you please investigate and fix the issue and/or forward
my bug report upstream?

Thanks for your time!
Bye.




-- System Information:
Debian Release: stretch/sid
  APT prefers testing
  APT policy: (800, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 4.3.0-1-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)

Versions of packages xul-ext-cookie-monster depends on:
ii  iceweasel  43.0.2-1+b1

xul-ext-cookie-monster recommends no packages.

xul-ext-cookie-monster suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message ---
Source: cookie-monster
Source-Version: 1.3.0.0-1


On Sat, 9 Jan 2016 15:20:09 -0400 David Prévot wrote:

> Hi Francesco,

Hello David,

> 
> Thank you for your report.

You're welcome!
Thanks to you for your quick reaction.   :-)

> 
> On Tue, Jan 05, 2016 at 01:39:13PM +0100, Francesco Poli (wintermute) wrote:
> > Package: xul-ext-cookie-monster
> > Version: 1.2.5-1
> 
> > I noticed a regression, after the recent
> > 
> >   [UPGRADE] iceweasel:amd64 38.5.0esr-1 -> 43.0.2-1
> >   [UPGRADE] iceweasel:amd64 43.0.2-1 -> 43.0.2-1+b1
> > 
> > I can no longer login on www.amazon.it or www.amazon.com, even after
> > temporarily allowing all cookies.
[...]
> The just uploaded 1.3.0.0-1 version package is supposed to fix handling
> of HTTP and HTTPS
[...]
> 
> Please let us know (or directly close the bug with version 1.3.0.0-1) if
> upgrading is enough to fix your issue.

The new upstream version indeed seems to fix the issue.
I am consequently closing the bug report with version 1.3.0.0-1 .

Thanks a lot for your help.   :-)
I wish all package maintainers dealt with bug reports this way.

Bye!


-- 
 http://www.inventati.org/frx/
 There's not a second to spare! To the laboratory!
..................................................... Francesco Poli .
 GnuPG key fpr == CA01 1147 9CD2 EFDF FB82  3925 3E1C 27E1 1F69 BFFE

Attachment: pgpkCrFtGdHVi.pgp
Description: PGP signature


--- End Message ---
_______________________________________________
Pkg-mozext-maintainers mailing list
Pkg-mozext-maintainers@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-mozext-maintainers

Reply via email to