InformAction Forums

When this feature was introduced I verified that the header was being sent properly, and modified a simple click tracker I use on my own site to honor the header.

Later on, I decided to modify the behavior further, but for some reason I could never "see" a X-Do-Not-Track header being sent to my local development and testing server. I finally installed Modify Headers and set the X-Do-Not-Track header there, and suddenly my click tracker was seeing the header again.

I tried going into about:config and modifying the noscript.doNotTrack.* preferences--especially the "forced" preference--but got no change.

I was later able to verify that the header is sent for non-LAN addresses, so I suspect this involved with the "fix" for the header breaking some routers.

Yes, it is part of the work-around.
No real "fix" is possible, since it's a router bug.
Anyway I can't see any usefulness in sending the header to private addresses.

Then please at least allow the noscript.doNotTrack.forced preference to re-enable it for LAN addresses, for those in situations like mine.

Heptite wrote:Then please at least allow the noscript.doNotTrack.forced preference to re-enable it for LAN addresses, for those in situations like mine.

It will be done in next dev build.

Done in latest development build.