1514246 - Tracking Protection Report not working

Status: RESOLVED MOVED

(Web Compatibility :: Tooling & Investigations, defect, P3)

Description

[Wellington Torrejais da Silva]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0

Steps to reproduce:

- Open site:

- Blank page
- But work with track protection disable.
- Try to report with favicon menu context
- No visible errors
- But error at Browser console:

13:45:28.329 XHRPOSThttps://tracking-protection-issues.herokuapp.com/new[HTTP/1.1 422 UNPROCESSABLE ENTITY 2882ms] 
HeadersCookiesParamsResponseTimingsStack TraceSecurityRequest URL:https://tracking-protection-issues.herokuapp.com/newRequest method:POSTRemote address:54.236.166.251:443Status code:422Edit and ResendRaw headersVersion:HTTP/1.1Response headers (199 B)Connectionkeep-aliveContent-Length40Content-Typetext/html; charset=utf-8DateFri, 14 Dec 2018 15:45:29 GMTServergunicorn/19.9.0Via1.1 vegurRequest headers (404 B)Accept*/*Accept-Encodinggzip, deflate, brAccept-Languageen-US,en;q=0.5Connectionkeep-aliveContent-Length1039content-typemultipart/form-data; boundary=…39755485020227936031255584007DNT1Hosttracking-protection-issues.herokuapp.comOriginnullUser-AgentMozilla/5.0 (X11; Linux x86_64…) Gecko/20100101 Firefox/66.0


Actual results:

Error when try to report tracking protection error from firefox interface:

====

13:45:28.329 XHRPOSThttps://tracking-protection-issues.herokuapp.com/new[HTTP/1.1 422 UNPROCESSABLE ENTITY 2882ms] 
HeadersCookiesParamsResponseTimingsStack TraceSecurityRequest URL:https://tracking-protection-issues.herokuapp.com/newRequest method:POSTRemote address:54.236.166.251:443Status code:422Edit and ResendRaw headersVersion:HTTP/1.1Response headers (199 B)Connectionkeep-aliveContent-Length40Content-Typetext/html; charset=utf-8DateFri, 14 Dec 2018 15:45:29 GMTServergunicorn/19.9.0Via1.1 vegurRequest headers (404 B)Accept*/*Accept-Encodinggzip, deflate, brAccept-Languageen-US,en;q=0.5Connectionkeep-aliveContent-Length1039content-typemultipart/form-data; boundary=…39755485020227936031255584007DNT1Hosttracking-protection-issues.herokuapp.comOriginnullUser-AgentMozilla/5.0 (X11; Linux x86_64…) Gecko/20100101 Firefox/66.0

===


Expected results:

No errors, server up, and report working.

Comment 1

[Wellington Torrejais da Silva]

The site: https://www.startse.com/noticia/nova-economia/59016/google-museu-nacional-14-12-18

Comment 2

[Wellington Torrejais da Silva]

(In reply to Wellington Torrejais da Silva from comment #1)
> The site:
> https://www.startse.com/noticia/nova-economia/59016/google-museu-nacional-14-
> 12-18

Not working? https://tracking-protection-issues.herokuapp.com/

Comment 3

[Marcia Knous [:marcia]]

Moving to a better component.

Comment 4

[Johann Hofmann [:johannh]]

I can't reproduce this, it might have been a temporary issue with the server. Can you still reproduce this? If yes, it might be good if you could attach the full request (including the form data) from the network panel.

Thanks!

Comment 5

[Wellington Torrejais da Silva]

Hi,

New test, when report this site problem(https://powerboard.basemark.com/home):

20:22:01.899 Content Blocking report to https://tracking-protection-issues.herokuapp.com/new failed with status 422 browser-contentblocking.js:784

and

20:22:14.590 Error while detaching the browsing context target front: Connection closed, pending request to server1.conn0.parentProcessTarget1, type detach failed

Request stack:
request@resource://devtools/shared/protocol.js:1415:14
generateRequestMethods/</frontProto[name]@resource://devtools/shared/protocol.js:1539:14
detach@resource://devtools/shared/fronts/targets/browsing-context.js:100:24
async*destroy/this._destroyer<@resource://devtools/client/framework/target.js:791:17
async*destroy@resource://devtools/client/framework/target.js:766:24
eventSource/proto.emit@resource://devtools/shared/client/event-source.js:128:9
onClosed@resource://devtools/shared/client/debugger-client.js:890:5
close@resource://devtools/shared/transport/local-transport.js:154:9
close@resource://devtools/shared/transport/local-transport.js:150:7
close@resource://devtools/shared/transport/local-transport.js:150:7
cleanup@resource://devtools/shared/client/debugger-client.js:300:9
detachClients@resource://devtools/shared/client/debugger-client.js:325:9
safeOnResponse@resource://devtools/shared/client/debugger-client.js:506:14
listenerJson@resource://devtools/shared/client/debugger-client.js:529:26
emit@resource://devtools/shared/event-emitter.js:186:15
emit@resource://devtools/shared/event-emitter.js:267:5
emitReply@resource://devtools/shared/client/debugger-client.js:810:31
DevTools RDP*request@resource://devtools/shared/client/debugger-client.js:519:21
stopListeners@resource://devtools/shared/webconsole/client.js:677:12
detach@resource://devtools/shared/webconsole/client.js:712:5
detachClients@resource://devtools/shared/client/debugger-client.js:329:9
close@resource://devtools/shared/client/debugger-client.js:334:5
destroy/this._bcDestroyer<@resource://devtools/client/webconsole/browser-console.js:99:13
async*destroy@resource://devtools/client/webconsole/browser-console.js:93:26
init/<@resource://devtools/client/webconsole/browser-console.js:69:7
EventListener.handleEvent*init@resource://devtools/client/webconsole/browser-console.js:68:5
openBrowserConsole@resource://devtools/client/webconsole/hudservice.js:102:12
toggleBrowserConsole/this._browserConsoleInitializing<@resource://devtools/client/webconsole/hudservice.js:163:15
async*toggleBrowserConsole@resource://devtools/client/webconsole/hudservice.js:158:41
async*openBrowserConsoleOrFocus@resource://devtools/client/webconsole/hudservice.js:182:12
onKeyShortcut@resource://devtools/client/framework/devtools-browser.js:274:9
async*onKey@jar:file:///home/wellington/softwares/firefox/browser/omni.ja!/components/devtools-startup.js:606:15
async*hookKeyShortcuts/xulKey<@jar:file:///home/wellington/softwares/firefox/browser/omni.ja!/components/devtools-startup.js:583:53
EventListener.handleEvent*createKey@jar:file:///home/wellington/softwares/firefox/browser/omni.ja!/components/devtools-startup.js:630:5
hookKeyShortcuts@jar:file:///home/wellington/softwares/firefox/browser/omni.ja!/components/devtools-startup.js:583:22
hookWindow@jar:file:///home/wellington/softwares/firefox/browser/omni.ja!/components/devtools-startup.js:357:5
onWindowReady@jar:file:///home/wellington/softwares/firefox/browser/omni.ja!/components/devtools-startup.js:296:5
_delayedStartup@chrome://browser/content/browser.js:1580:5
EventListener.handleEvent*onLoad@chrome://browser/content/browser.js:1402:5
EventHandlerNonNull*@chrome://browser/content/browser.xul:105:19
 browsing-context.js:102:7

Thanks!

Comment 6

[Johann Hofmann [:johannh]]

Forwarding this to Mike since it seems like a server issue, Mike, is there anything we can do here? Do you have server logs that may be able to say what's going wrong (which entity was unprocessable)?

Comment 7

[Mike Taylor [:miketaylr]]

(In reply to Wellington Torrejais da Silva from comment #2)

(In reply to Wellington Torrejais da Silva from comment #1)

The site:
https://www.startse.com/noticia/nova-economia/59016/google-museu-nacional-14-
12-18

Not working? https://tracking-protection-issues.herokuapp.com/

This is expected behavior (just seeing 200OK in response to a GET).

Thanks for reporting the issue Wellington... I'm not able to reproduce it from either of the sites that you provided (I see 201 in the logs).

We don't log any information that would help us understand why this would fail right now (trying to preserve privacy as much as possible by collecting basically no info).

Looking at what logs we do have (only 1500 lines are kept), I see 16 / 1500 422 responses, so roughly 1% of requests are failing. Let's close this bug here and I'll continue investigation over in https://github.com/mozilla/tracking-protection-issues/issues/7.

(I can't close this as a dupe of a GitHub issue, so I'll just awkwardly close it as INVALID -- but it's a real bug I'd like to fix).