EasyPrivacy and "pagespeed_beacon" requests

[jimpop]

Hello,

The pagespeed [1] moduule for Apache/Nginx/etc utilizes a URL POST callback mechanism to /pagespeed_beacon?... which contains pagespeed session data. This is currently blocked by EasyPrivacy's " _beacon?" rule [2]. Pagespeed is not leaking privacy data back to the same server the original http request was sent to, it is merely interacting with the same server the original http request was sent to.

1) https://developers.google.com/speed/pagespeed/module/

2) https://easylist-downloads.adblockplus. ... rivacy.txt

[lewisje]

I hope this whitelist rule won't cause too many false negatives, but I'll go ahead and put it in my custom filters:

Code: Select all

@@/pagespeed_beacon?$~third-party,xmlhttprequest

I'm not sure whether this would count as an image, xmlhttprequest, etc., but if I could know for sure I'd put one of those specifiers in too, to make this whitelist more tailored.
EDIT: added the xmlhttprequest specifier

Also you should complain on the EasyList forum for incorrectly removed content: http://forums.lanik.us/viewforum.php?f=64

[jimpop]

It's an xmlhttprequest call back to the origin server used to track page performance. Pagespeed runs on a webserver and optimizes outbound html, js, css. The callback to /pagespeed_beacon is for perf data related to those page optimizations.