i have an issue with the caching of typo3. The scenario is i have the base: www.domain.com and another base variant cache.domain.com. It seems like the cache tables are only cleared per domain e.g. if i’m in the backend of chache.domain.com it will only clear the db entries for that particular domain. The cf_cache_hash table has still content. After i clear the cache in the www backend the table is empty.
Is this behavior correct? And if so how can i clear with one backend everything?
Many thanks for any suggestions and advice
Kind regards
Jan
I cannot reproduce this. Clearing frontend caches will clear for all domains.
Related
I am working on zend framework, I can see when i load the because it is getting lots of time to load, and in mysql database there are more than 250+ connections open, I am using zend 1 framework, can anyone please help me what we can do to resolve this issue ? any help will be really appreciated
Those 250+ connection, are in production environment or in test?
How many user that make requests do you have?
Are you using Db or multiDb resource?
Does your html pages make async requests once loaded?
There are lots of variables to keep in consideration to debug this issue
I'm doing some planning for replacing an existing solution with mongodb and potentially using the GridFS functionality for static assets. One question that I have is if I choose to front GridFS with nginx, is there a way to control which assets in a collection may be served directly from nginx versus which asset requests need to be directed to my application?
The reason I ask is that some security checks are done for certain assets and those assets have always been served out of the app itself (and will need to continue to be, at least for now).
I was thinking, I could probably just add a property on the file descriptors stored in nginx that is something like isPublished. Could I instruct nginx-gridfs to respect this property?
Looks like there have been requests for this functionality but the project is largely abandoned by contributors. The applicable ticket is here: https://github.com/mdirolf/nginx-gridfs/issues/24
I've got a highly trafficed website and I'm using Sails for a specific conponent on a page. However the information doesn't change that often, maybe once per day. I'm wondering if there is a way to do view caching? Ideally using a key/store like Redis?
You can run your app behind a proper webserver like NGINX or Apache and set them up to cache.
I'd like to know if is possible to use memcached as the default storage for Varnish cache.
Searching on the web I found https://github.com/sodabrew/libvmod-memcached but the examples that I found so far was just about manually storing/retrieving the content on memcached using VCL rules.
What I'm looking for is memcached as the default storage for Varnish, just like we do with file/memory today.
Is there some way to do this ? Thanks in advance
Please have a look at the architecture document on Varnish. You can see the designer had specific ideas on the backend (all in memory, let the kernel decide what goes to swap/disk). Memcache doesn't really fit there. Can you explain why Varnish as-is is insufficient, and you want memcache as the back-end of varnish?
If you want a front-end cache based on memcache, there are probably other solutions or you could write one. I wouldn't pick Varnish just for the VCL language, as I think it's a complex language to accomplish proper caching.
I got 2 domains bought at diferent providers and I would like http://aaaaa.com to show http://bbbbb.com/aaaaa
Is this possible using only DNS? must I transfer the domain to my hosting provider that has the http://bbbb.com domain? I really don't want to use a redirection or iframe.
Thank you for your help!
You can do that on DNS Level in two ways:
Depending on your Provider you can make http://DomainA.com/ redirect with masking to http://DomainB/Folder now this is premature way of doing it specially if SEO matters to you.
If you have your own servers or you can add Virtual Directory on the server you can point DomainA to this server and make http://DomainB/Folder location as start point.
This can be done with Apache, Nginx or IIS.
Please can you give me more explanations on what OS and what kind of hosting you have so i can help you with this? And also what kind of application because if your using .net its a bit different then using normal PHP or HTML or wordpress... U will need to add Virtual Directory to achieve this.
If your using shared hosting and have Apache web-server the easiest way to do it is so:
.htaccess and Apache also can handle such redirection.
http://www.site5.com/blog/apache/htaccess/redirect-to-blog/20090427/
Regards and hope this helps.