Hey guys, I was trying to set cache-control headers today (see old emails below) and seem to bump into the same issue: both dev and production servers always respond with "cache-control: no-cache".
Just wanted to check in and see whether this is me or the feature isn't available yet.
There doesn't seem to be anything related on the public issues tracker.
Thanks!
-- alex
---------- Forwarded message ----------
From: "Danny Hermes" <dhe...@google.com>
Date: Nov 2, 2012 12:33 AM
Subject: Re: Python Endpoints Expires headers
> Doug,
>
> Thanks for bringing this up. It appears we are missing a piece here and we are looking into it.
>
> We will be distributing a new version of the code soon, and hopefully a fix will be in place.
>
> I'll update this thread once it is nailed down.
>
>
> On Wed, Oct 31, 2012 at 6:43 PM, Doug Chestnut <dougch...@gmail.com> wrote:
>>
>> So i've looked into this a little more and have tried this with no
>> success (same response headers as before):
>>
>> @endpoints.method(CatalogRequest, CatalogQueryResponse,
>> path="catalog", http_method='GET', name="catalog.query",
>> cache_control=CacheControl(CacheControl.PRIVATE,100) )
>> def CatalogQuery(self, request):
>> ...
>>
>> On Wed, Oct 31, 2012 at 3:21 PM, Doug Chestnut <dougch...@gmail.com> wrote:
>> > Sorry if this question has been asked and answered already. Is there
>> > a way to set the expires headers for endpoint responses so they get
>> > cached by the browser? I'm seeing headers like
>> > "cache-control:no-cache, no-store, max-age=0, must-revalidate" and
>> > "expires:Fri, 01 Jan 1990 00:00:00 GMT" in my responses currently.
>> >
>> > Thanks,
>> > --Doug
>>
>
>
>
> --
> Danny Hermes
> Developer Programs Engineer