subject:"Re\: Use CDN for djangoproject.com"
from which an identical set of static files was served).
>> correctly fastly has a fantastic live dashboard with all of this info.
> collect some slightly more interesting numbers after a week or two.
>> these and forward on http 1.1 requests? Could you elaborate a bit?
> our case, Fastly originally provisioned a wildcard SSL cert ('*.
> described under "The Firefox way" in the link above.
> correctly fastly has a fantastic live dashboard with all of this info.
collect some slightly more interesting numbers after a week or two.
> and forward on http 1.1 requests? Could you elaborate a bit?
our case, Fastly originally provisioned a wildcard SSL cert ('*.
way" in the link above.
frustration and confusion in the meantime), so thank you again, Mariusz!
Looking good! Thanks for your work Tobias.
I get 30ms through CDN instead of 230ms from here in London, UK.
> primary domain, docs.djangoproject.com, so you shouldn't notice a change).
> me know if you see anything out of order.
> You can click on an individual region to see the variability over time.
>> anyone. If the need arises we can still manually purge the cache as needed.
>>> views have longer timeouts set (to 1 hour and 1 week, respectively).
>>> pushed out and cached.
>>> if the git checkout hasn't changed (in the update_docs management command).
primary domain, docs.djangoproject.com, so you shouldn't notice a change).
know if you see anything out of order.
> anyone. If the need arises we can still manually purge the cache as needed.
>> views have longer timeouts set (to 1 hour and 1 week, respectively).
>> be desirable to set the timeout to something greater than 5 minutes.
>> pushed out and cached.
>> if the git checkout hasn't changed (in the update_docs management command).
>> somewhere between 1 and 24 hours.
>> timeout for such pages?
>> updated) pages to timeout, in the event they do change?
anyone. If the need arises we can still manually purge the cache as needed.
> views have longer timeouts set (to 1 hour and 1 week, respectively).
> be desirable to set the timeout to something greater than 5 minutes.
> pushed out and cached.
> if the git checkout hasn't changed (in the update_docs management command).
> somewhere between 1 and 24 hours.
> updated) pages to timeout, in the event they do change?
>> Thanks for sharing the results.
>>> Thanks for the test site, Tobias.
www.python.org is an alias for dualstack.python.map.fastly.net.
That's great! Thanks for the feedback.
> for the dev builds, I guess).
> probably need to edit /etc/hosts).
>> be OK I think.
views have longer timeouts set (to 1 hour and 1 week, respectively).
already been pushed out and cached.
if the git checkout hasn't changed (in the update_docs management command).
somewhere between 1 and 24 hours.
specific). The same page on docs.djangoproject.com responds in 800–900ms.
for the dev builds, I guess).
> be OK I think.
>>> somewhere between 1 and 24 hours.
>>> timeout for such pages?
>>> updated) pages to timeout, in the event they do change?
> Thanks for the test site, Tobias.
invalidating the whole cache if needed, it seems the simplest solution.
>>> Thanks for sharing the results.
Thanks for the test site, Tobias.
> www.python.org is an alias for dualstack.python.map.fastly.net.
> avoid them. They run an old fork of Varnish which is not fun to configure.
be desirable to set the timeout to something greater than 5 minutes.
pages to timeout, in the event they do change?
> Thanks for sharing the results.
>> Thanks for the test site, Tobias.
>>> www.python.org is an alias for dualstack.python.map.fastly.net.
them. They run an old fork of Varnish which is not fun to configure.
> authenticated comms all the way through (terminate and reconnect).
On Thu, Feb 14, 2019, 11:49 PM Cheng C  Thanks for the test site, Tobias.
>> www.python.org is an alias for dualstack.python.map.fastly.net.
>>> them. They run an old fork of Varnish which is not fun to configure.
authenticated comms all the way through (terminate and reconnect).
hosting the same name so that DNS alone can decide to hit cdn or origin.
> serve sensitive build artefacts?
> several large Linux distributions use them to serve cached apt packages.
> (and therefore interception) at their end.
>> restrictions on where you're allowed to download software from.
>> moving the docs behind that.
>> them. They run an old fork of Varnish which is not fun to configure.
>>> authenticated comms all the way through (terminate and reconnect).
>>> hosting the same name so that DNS alone can decide to hit cdn or origin.
>>> expertise their teams have.
several large Linux distributions use them to serve cached apt packages.
(and therefore interception) at their end.
> restrictions on where you're allowed to download software from.
> moving the docs behind that.
> > to the CDN provider.
> them. They run an old fork of Varnish which is not fun to configure.
>> authenticated comms all the way through (terminate and reconnect).
>> hosting the same name so that DNS alone can decide to hit cdn or origin.
>> Anyway, it seems weird to me to dismiss a CDN offhand “because security”.
>>> several large Linux distributions use them to serve cached apt packages.
>>> therefore interception) at their end.
restrictions on where you're allowed to download software from.
moving the docs behind that.
> to the CDN provider.
very comparable service for a fraction of the cost of CloudFront.
the docs are updated. But I’m sure there’s something I’m missing.
> hosting the same name so that DNS alone can decide to hit cdn or origin.
> Anyway, it seems weird to me to dismiss a CDN offhand “because security”.
>> several large Linux distributions use them to serve cached apt packages.
>> therefore interception) at their end.
>>> restrictions on where you're allowed to download software from.
>>> moving the docs behind that.
>>> > to the CDN provider.
>>> very comparable service for a fraction of the cost of CloudFront.
>>> docs are updated. But I’m sure there’s something I’m missing.
>>> probably behind a CDN.
>>> provide free service for django as well.
someone who does, feel free to email/introduce me off list, too.
> therefore interception) at their end.
>> > to the CDN provider.
>> very comparable service for a fraction of the cost of CloudFront.
>> docs are updated. But I’m sure there’s something I’m missing.
>> probably behind a CDN.
>> provide free service for django as well.
>> time visit, so DNS query time might not be included).
>> >  Best regards and thanks for all your great work.
>> Groups "Django developers (Contributions to Django itself)" group.
>> send an email to django-developers+unsubscr...@googlegroups.com.
Anyway, it seems weird to me to dismiss a CDN offhand “because security”.
large Linux distributions use them to serve cached apt packages.
therefore interception) at their end.
> comparable service for a fraction of the cost of CloudFront.
> docs are updated. But I’m sure there’s something I’m missing.
> provide free service for django as well.
> time visit, so DNS query time might not be included).
> >  Best regards and thanks for all your great work.
> Groups "Django developers (Contributions to Django itself)" group.
> send an email to django-developers+unsubscr...@googlegroups.com.
> > >>  For more options, visit https://groups.google.com/d/optout.
> Why do we not want to use Cloudflare?
something I need from a CDN.
> > comparable service for a fraction of the cost of CloudFront.
> > curious if anyone has any general objections to a CDN of any kind.
> > are updated. But I’m sure there’s something I’m missing.
> >>> behind a CDN.
>  provide free service for django as well.
>  visit, so DNS query time might not be included).
>  Best regards and thanks for all your great work.
> >> "Django developers (Contributions to Django itself)" group.
> >> email to django-developers+unsubscr...@googlegroups.com.
> >>  To post to this group, send email to django-developers@googlegroups.com.
> >>  Visit this group at https://groups.google.com/group/django-developers.
> >>  For more options, visit https://groups.google.com/d/optout.
> > "Django developers (Contributions to Django itself)" group.
> > email to django-developers+unsubscr...@googlegroups.com.
> >  To post to this group, send email to django-developers@googlegroups.com.
> >  Visit this group at https://groups.google.com/group/django-developers.
> >  For more options, visit https://groups.google.com/d/optout.
> Anyways, at this stage let’s not get bogged down on provider decisions.
> I’m curious if anyone has any general objections to a CDN of any kind.
> are updated. But I’m sure there’s something I’m missing.
provide free service for django as well.
visit, so DNS query time might not be included).
Best regards and thanks for all your great work.
>> "Django developers (Contributions to Django itself)" group.
>> To post to this group, send email to django-developers@googlegroups.com.
>> Visit this group at https://groups.google.com/group/django-developers.
comparable service for a fraction of the cost of CloudFront.
curious if anyone has any general objections to a CDN of any kind.
are updated. But I’m sure there’s something I’m missing.
>>> visit, so DNS query time might not be included).
>>> Best regards and thanks for all your great work.
and works really, really well.
>> visit, so DNS query time might not be included).
>> Best regards and thanks for all your great work.
Why do we not want to use Cloudflare?
> visit, so DNS query time might not be included).
> Best regards and thanks for all your great work.