New issue
Advanced search Search tips

Issue 688752 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Apr 2018
Cc:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Compat



Sign in to add a comment

Notifications button returns error 403 on https://goo.gl

Reported by alex...@gmail.com, Feb 4 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/55.0.2883.87 Safari/537.36

Example URL:
https://goo.gl/

Steps to reproduce the problem:
1. Go to https://goo.gl/
2. Click the notifications button in the top right (need to be signed in into a google account)

What is the expected behavior?
Notifications should be displayed just as on google.com

What went wrong?
Clicking the notifications button will either return a 403 error or display the notification menu with an "error loading" popup. 

Does it occur on multiple sites: No

Is it a problem with a plugin? No 

Did this work before? N/A 

Does this work in other browsers? N/A

Chrome version: 55.0.2883.87  Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 24.0 r0

 
The error remains. When I went to https://goo.gl/ and clicked in notifications, the 403 error showed to me. Follows the evidence attached.

Chrome version: 55.0.2883.87

error403.png
108 KB View Download
Labels: Needs-Milestone

Comment 3 by ajha@chromium.org, Feb 7 2017

Cc: ajha@chromium.org
Components: Infra
Labels: -OS-Windows -Needs-Milestone OS-All
Status: Untriaged (was: Unconfirmed)
This doesn't looks to be specific to Chrome as the same behavior is seen on Firefox as well. Tested on Mac OS 10.12.5.

Not sure what should be correct label and who should get this. Marking this as Untriaged and Adding Infra for more inputs.
Components: -Infra
ajha@ if this has anything to do with chrome infrastructure, please be specific. I think this has to do with either browsers or websites (incl. frameworks that website use), not continuous integration that Chrome infra provides.
Same for my with Firefox 51.0.1, exact same error in same conditions.
Status: WontFix (was: Untriaged)
Site issue not a chrome issue. Happens in Firefox.

Sign in to add a comment