When the settings are
In the settings.yml
prod:
.settings:
no_script_name: on
logging_enabled: off
cache: on
etag: on
In the cache.yml
default:
enabled: on
with_layout: true
lifetime: 86400
client_lifetime: 0
then in the headers, etag, last-modified headers are coming with
response. And the changes made in the database is not reflecting in
the downloaded content without clearing the cache in the server
(symfony clear cache command)
But when the settings are
In the settings.yml
prod:
.settings:
no_script_name: on
logging_enabled: off
cache: false
etag: on
In the cache.yml
default:
enabled: false
with_layout: true
lifetime: 86400
client_lifetime: 0
then in the headers, etag, last-modified headers are not coming with
response. And the changes made in the database is reflecting immedetly
(in the next request after modification) in the downloaded content.
For this no need to clear cache in the server?
can somebody help me?
I am using Poster plugin of firefox to test the rest apis.
regards
Shihab
On Nov 8, 12:17 pm, pghoratiu <pghora...@gmail.com> wrote:
> You have to check the browser HTTP headers that are sent (Request/
> Response) via Firebug or HttpFox Firefox extensions.
> Do you have enabled caching for your page?
> There are more things to consider when you try to cache a page, not
> just the Etag.
>
> gabriel
>
> On Nov 8, 7:28 am, Shihab KB <shiha...@gmail.com> wrote:
>
>
>
> > Thank you for your answer. I am trying to implement ETag in my restful
> > apis. I have a problem here. Please check this and could you please
> > give me a solution?
>
> > Hi,
>
> > I am trying to implement etag feature in my RESTFul web services. I
> > heard that etag is a mechanism that HTTP provides for cache
> > validation, and which allows a client to make conditional requests and
> > saves bandwidth, as a web server does not need to send a full response
> > if the content has not changed. I have manged to implement the etag
> > feature as given below.
>
> > In the settings.yml
> > prod:
> > .settings:
> > no_script_name: on
> > logging_enabled: off
> > cache: on
> > etag: on
>
> > In the cache.yml
> > default:
> > enabled: on
> > with_layout: true
> > lifetime: 86400
> > client_lifetime: 0
>
> > But I have one issue that, after implementing this, when I modified
> > the content in the database, the client is receiving only previous
> > data. Not modified one. When I reset the above settings (setting.yml
> > and cache.yml) its working fine.
>
> > Have faced same situation? Can you suggest a way to overcome this?
>
> > My client application is a .NET application.
>
> > regards
> > Shihab
>
> > On Nov 5, 3:10 pm, Gareth McCumskey <gmccums...@gmail.com> wrote:
>
> > > ETag is just a way to have finer grained control over caching and to
> > > manage
> > > when to reprocess a request or just send back a cached response. So for
> > > example, if you send a GET request for a resource with id 10 and get a
> > > result, sending a request later for id 10 should respond back with the
> > > cached version if the resource of id 10 has not changed but reprocess the
> > > request if it has changed.
>
> > > On Fri, Nov 5, 2010 at 8:29 AM, Shihab KB <shiha...@gmail.com> wrote:
> > > > Dear friends,
>
> > > > Can you explain me the significance and benefits of enabling the ETag
> > > > feature ?
>
> > > > regards
> > > > Shihab
>
> > > > --
> > > > If you want to report a vulnerability issue on symfony, please send it
> > > > to
> > > > security at symfony-project.com
>
> > > > You received this message because you are subscribed to the Google
> > > > Groups "symfony users" group.
> > > > To post to this group, send email to symfony-users@googlegroups.com
> > > > To unsubscribe from this group, send email to
> > > > symfony-users+unsubscr...@googlegroups.com<symfony-users%2bunsubscr...@goog
> > > > legroups.com>
> > > > For more options, visit this group at
> > > >http://groups.google.com/group/symfony-users?hl=en
>
> > > --
> > > Gareth McCumskeyhttp://garethmccumskey.blogspot.com
> > > twitter: @garethmcc- Hide quoted text -
>
> > > - Show quoted text -- Hide quoted text -
>
> - Show quoted text -
--
If you want to report a vulnerability issue on symfony, please send it to
security at symfony-project.com
You received this message because you are subscribed to the Google
Groups "symfony users" group.
To post to this group, send email to symfony-users@googlegroups.com
To unsubscribe from this group, send email to
symfony-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/symfony-users?hl=en
