[pydotorg-www] [Infrastructure] Access to www.python.org without going through the cache

Donald Stufft donald at stufft.io
Mon Jun 2 14:01:08 CEST 2014


Oh another handy thing, anyone can purge a single URL from the Fastly cache, it
doesn’t require authentication. 

curl -X PURGE https://www.python.org/whatever/

On Jun 2, 2014, at 7:59 AM, M.-A. Lemburg <mal at python.org> wrote:

> On 02.06.2014 13:52, Donald Stufft wrote:
>> A better solution still would be to use the purge API so that editing a page purges the cached
>> copy of the page and the update is available to everyone immediately. This is what PyPI does to
>> allow Fastly to cache things for 1 day but still have near instant availability of new package
>> uploads and the like.
> 
> Well, of course :-) I just figure that it's easier to simply bypass
> Fastly than to implement the full cache invalidation logic.
> 
> Note: Even more better would be to have a preview button in the CMS
> admin interface for the site. At the moment, we're doing live edits
> on a production with no means to even undo changes... not exactly
> state of the art CMS.
> 
>> I just figured i’d mention the kludge since it’s better than trying to wait :)
> 
> Thanks for the trick. It does help indeed :-)
> 
>> On Jun 2, 2014, at 7:50 AM, M.-A. Lemburg <mal at python.org> wrote:
>> 
>>> On 02.06.2014 12:48, Donald Stufft wrote:
>>>> It’s kind of a kludge, but just add a parameter to the URL, like ?foo=12332131 the full URL
>>>> is used as part of the cache key.
>>> 
>>> Thanks, this does work, but it would still be better to have a domain which can be used for
>>> testing the edits immediately and without having to hand edit each page URL (and remember to
>>> bump the foo value for each edit cycle), something like www.int.python.org or 
>>> www-nocache.python.org.
>>> 
>>>> On Jun 2, 2014, at 4:55 AM, M.-A. Lemburg <mal at python.org> wrote:
>>>> 
>>>>> When editing pages on the python.org website, it is very difficult to tell whether edits
>>>>> are correct or not, since it takes ages for the caches to receive the updates from the
>>>>> Django CMS.
>>>>> 
>>>>> Is there a way, perhaps a special URL, to directly access the backend system without
>>>>> going through Fastly ?
>>>>> 
>>>>> Thanks, -- Marc-Andre Lemburg Director Python Software Foundation
>>>>> http://www.python.org/psf/ ________________________________________________
>>>>> Infrastructure mailing list Infrastructure at python.org
>>>>> https://mail.python.org/mailman/listinfo/infrastructure Unsubscribe:
>>>>> https://mail.python.org/mailman/options/infrastructure/donald%40stufft.io
>>>> 
>>>> 
>>>> ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F
>>>> 6E3C BCE9 3372 DCFA
>>>> 
>>>> 
>>>> 
>>>> ________________________________________________ Infrastructure mailing list 
>>>> Infrastructure at python.org https://mail.python.org/mailman/listinfo/infrastructure
>>>> Unsubscribe: https://mail.python.org/mailman/options/infrastructure/mal%40egenix.com
>>>> 
>>> 
>>> -- Marc-Andre Lemburg Director Python Software Foundation http://www.python.org/psf/
>> 
>> 
>> ----------------- Donald Stufft PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C
>> BCE9 3372 DCFA
>> 
>> 
>> 
>> _______________________________________________ pydotorg-www mailing list 
>> pydotorg-www at python.org https://mail.python.org/mailman/listinfo/pydotorg-www
>> 
> 
> -- 
> Marc-Andre Lemburg
> Director
> Python Software Foundation
> http://www.python.org/psf/


-----------------
Donald Stufft
PGP: 0x6E3CBCE93372DCFA // 7C6B 7C5D 5E2B 6356 A926 F04F 6E3C BCE9 3372 DCFA

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://mail.python.org/pipermail/pydotorg-www/attachments/20140602/b6c87dda/attachment.sig>


More information about the pydotorg-www mailing list