Neat, I didn't know AWS had an AnyCast service like that. The Cloudflare workers issue is a bit disappointing, I remember their blog about eliminating cold starts and how clever it seemed, but I guess it's still not there? On another note have you evaluated fly.io at all for this? This looks right in their wheelhouse of many regions + AnyCast + IPv6, and I could definitely see configuration being simpler with them th…
The fastest de-referer service... with AWS Global Accelerator
11–20 of 79 posts
Re: The fastest de-referer service... with AWS Global Accelerator
#12Re: The fastest de-referer service... with AWS Global Accelerator
#13Neat, I didn't know AWS had an AnyCast service like that. The Cloudflare workers issue is a bit disappointing, I remember their blog about eliminating cold starts and how clever it seemed, but I guess it's still not there? On another note have you evaluated fly.io at all for this? This looks right in their wheelhouse of many regions + AnyCast + IPv6, and I could definitely see configuration being simpler with them th…
The cloudflare workers issue should be resolved now, they eliminated cold starts in 2020 ( https://blog.cloudflare.com/eliminating-cold-starts-with-clo... ) and it seems like he tested it in 2019
Re: The fastest de-referer service... with AWS Global Accelerator
#14Earlier quoted context omitted.
Looks to be a service to remove the HTTP referer header when linking to other sites. Say your on example.com and click a a link to foo.com the browser will send the http header `Referer: example.com` in the HTTP get to foo.com, this means foo.com can then track how you came to their site.
LOL, why do you need an "accelerator" for this?
Re: The fastest de-referer service... with AWS Global Accelerator
#15This exact setup is easier on Fly.io - our proxy layer runs in 20 regions worldwide with anycast, so your requests hit the nearest region and quickly terminate TLS there.
You can also run any Docker container, and either choose regions to run them in, or just set the min/max and ask us to start and stop containers in whichever region has demand, so your deployment follows the sun.
Re: The fastest de-referer service... with AWS Global Accelerator
#16Full disclosure, I work at Fly.io now. This exact setup is easier on Fly.io - our proxy layer runs in 20 regions worldwide with anycast, so your requests hit the nearest region and quickly terminate TLS there. You can also run any Docker container, and either choose regions to run them in, or just set the min/max and ask us to start and stop containers in whichever region has demand, so your deployment follows the su…
Re: The fastest de-referer service... with AWS Global Accelerator
#17Using a Rwandan TLD negates pretty much all the effort in finding the fastest provider. No glue records and an unresponsive TLD nameserver translates into 100+ms for the initial DNS lookup (likely the only one that matters for such a service).
Re: The fastest de-referer service... with AWS Global Accelerator
#18Earlier quoted context omitted.
Looks to be a service to remove the HTTP referer header when linking to other sites. Say your on example.com and click a a link to foo.com the browser will send the http header `Referer: example.com` in the HTTP get to foo.com, this means foo.com can then track how you came to their site.
LOL, why do you need an "accelerator" for this?
Re: The fastest de-referer service... with AWS Global Accelerator
#19I read the first six paragraphs and still really had no idea what this is talking about. Can anyone help me understand?
Looks to be a service to remove the HTTP referer header when linking to other sites. Say your on example.com and click a a link to foo.com the browser will send the http header `Referer: example.com` in the HTTP get to foo.com, this means foo.com can then track how you came to their site.
Re: The fastest de-referer service... with AWS Global Accelerator
#20I read the first six paragraphs and still really had no idea what this is talking about. Can anyone help me understand?
If it was me, I would set referrer-policy: origin (or no-referrer) header[1] and avoid all the overhead. Supported on all current browsers[2], and no additional costs or code to worry about.
Also, does it seem a bit insecure to anyone else to outsource referrer stripping services if your goal is to secure the content of the referrer from third parties? How well do you trust the middlemen in this case?
1. https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Re...