Make the facilitator log, for each request, whether the proxy has set the flashproxy-allow cookie. This will allow us to estimate how much proxy capacity we will lose by going to opt-in-only.
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Child items
0
Show closed items
No child items are currently assigned. Use child items to break down this issue into smaller parts.
Linked items
0
Link issues together to show that they're related.
Learn more.
It occurs to me that we could also just require opt-in for a few days and see what happens. Proxies reload themselves every 24 hours because of a meta refresh in the embed. Make the switch, give them 24 hours to settle, then a day or two of measuring capacity, then switch back.
I have an implementation at https://github.com/aallai/flashproxy.git branch opt-in.The proxy sends the repr() of the cookie setting to facilitator.cgi, which then writes a timestamp and newline to the appropriate text file.
This is running now on the public facilitator (as of 2013-02-05 19:13:28 EST) and we are logging cookie values. I'll wait a few days and update the ticket.
It looks like about 2 or 3 percent of our current proxies have opted in. Marking this done because we got the logging done, now have to decide what to do with the results.
Trac: Status: needs_information to closed Resolution: N/Ato fixed
Actually I decided I don't want to keep the cookie logging forever. Let's turn it on again in the future if we need it. I pushed proxy code that doesn't send the cookie value at Thu Feb 21 13:04:51 PST 2013.