Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > alt.os.linux > #51490 > unrolled thread

nginx fix for the Facebook fbclid query

Back to article view | Back to alt.os.linux

Contents

  nginx fix for the Facebook fbclid query Nomen Nescio <noreply@mixnym.net> - 2018-11-02 09:10 -0500
    Re: nginx fix for the Facebook fbclid query Eli the Bearded <*@eli.users.panix.com> - 2018-11-02 21:15 +0000

#51490 — nginx fix for the Facebook fbclid query

Facebook now adds fbclid query string to URLs, busting CloudFlare’s 
cache.

See the last 3 or so messages here (you may have to hit enter to get 
down to them):

<https://community.cloudflare.com/t/facebook-now-adds-fbclid-query-string-to-urls-busting-cloudflares-cache/40355/46>

[toc] | [next] | [standalone]

#51500

In comp.os.linux.misc, Nomen Nescio  <noreply@mixnym.net> wrote:
> Facebook now adds fbclid query string to URLs, busting CloudFlare's 
> cache.

Yeah, it's not limited to CloudFlare.  This seems a particularly
stupid thing for Facebook to do. They are adding an extra parameter
to CGI queries on external sites.

I see about 10k of them in the logs on my site. It's not breaking any
caching for me, but I consider it extremely obnoxious and have been
weighing how to react.

I don't need the traffic, and I'm considering blocking everything with
fbclid in the URL. I'd like to have it throw up a message about why it
is blocked, hopefully in a way that makes users blame Facebook but I
haven't figured out how best to do that.

Elijah
------
runs a server for himself and just /lets/ other people use it

[toc] | [prev] | [standalone]

Back to top | Article view | alt.os.linux

csiph-web