archive-com.com » COM » E » ENFOLDSYSTEMS.COM

Total: 720

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Caching with EP
    will reply Nope That s an outdated version In this case Plone will send the updated version to Enfold Proxy which will pass it on to the browser and also replace the outdated version with the newer version X Cache MISS from www originalfunsite com Enfold Proxy now has an easy button in its interface to purge cached items for proxy definition s Enable split level caching in the Proxy Definition If your Plone caching add on supports it it is generally a good idea to enable split level caching for a proxy definition It only adding a single line to the eep ini file Read more about split level caching Next Step Verify that Your Cache Settings are in Effect The easiest way to verify your cache settings is to view the Enfold Proxy logs themselves That allows you to see the responses from Plone and also prevents browser issues from misleading you When viewing the Enfold Proxy logs be sure to activate the new Headers log level which is easier to read than typical HTTP headers To verify that caching is taking place from the browser look for this line in your HTTP response header X Cache HIT from www originalfunsite com If you see X Cache HIT then yes Enfold Proxy has sent you a cached version of this content item If you see X Cache MISS then no Enfold Proxy has sent you this content which was not in its cache Generally HIT s indicate successful caching Keep in mind that X Cache MISS is not always a bad thing For example if logged in as an administrator many resources will not be cached on purpose It s best to test as an anonymous web surfer i e someone who is not logged in If an item contains a modification then a MISS reply is mandatory Also object based caching like XSLT caching doesn t modify these headers so EP can be properly caching XSLT pages and still be sending out X Cache MISS headers Careful When testing it s a good idea to use two different browsers In Browser A such as Internet Explorer log in as Admin In Browser B i e Firefox log in as anonymous or as a logged in user It s also important to clear cache the right way and even to close the browser entirely if you don t the http headers you see won t be accurate Consult the troubleshooting checklist for caching To see the HTTP headers directly see Tools for Viewing Headers You should probably pick two or three sample items to check for headers Anything will do but at least one should be a graphic and one should be a Zope page such as http www originalfunsite com events Optimize Cache Settings and Measure Caching Performance See also Caching Goals and Strategies Many of your cache settings can be tweaked in whatever Plone product you are using to cache web items Note if you suspect

    Original URL path: http://www.enfoldsystems.com/software/proxy/docs/7.1/epcaching.html (2016-02-11)
    Open archived version from archive


  • How Caching Works
    upstream bandwidth usage and cost while significantly increasing performance For the most part a forward proxy server operates independently of Plone EP Proxy and is not really relevant to this document However some settings on the HTTP headers and plone app caching are geared to forward proxy servers so this document mentions it here simply to point out the potential for confusion A caching proxy server or reverse proxy receives web traffic to a site and returns cached content usually static content whenever possible Enfold Proxy is a caching proxy server because it forwards HTTP requests received from IIS to Plone only after first making sure that it does not have a cached version which it could return See the Enfold Proxy Architecture for more details In the context of Enfold Proxy we can break the concept even further according to caching method Disk based Cache The Cached item is saved on the proxy server s file system as a file This is probably the most common method RAM based Cache Because directories in Plone refer not to physical files but objects these items are not cached on the file system Instead they are cached as objects Object based cache is discussed in greater detail in the Caching XSLT topic Clearing Private Cache with your Browser Web surfers are used to clicking F5 or even clicking the Refresh button to obtain the latest version of a web page This doesn t clear the web cache and is not suitable for testing or troubleshooting caching issues Here is the right way to clear the cache in each browser Firefox Tools Clear Private Data Ctl Shift Delete You don t need to clear all the items here Just Cache is sufficient Internet Explorer 7 Tools Internet Options General Tab Browsing History Delete Delete Temporary Internet Files It is not necessary to delete cookies or the other items Viewing HTTP Headers There are several ways to watch HTTP headers First you can use the logs that are generated by Enfold Proxy After the October 2008 release Enfold Proxy now includes a special log level which shows HTTP headers and directional arrows in the log to indicate whether the request is coming or going Read more about how to view HTTP headers in the proxy log The second way is to install plugins in your browser that lets you view the headers in real time Because of the potential for confusion this second way is not recommended but mainly useful when you do not have access to the Enfold Proxy logs Below we will describe how to use browser plugins to view HTTP headers and how to interpret them The HTTP headers in the proxy log may have slight differences than what you see below but generally the syntax should be similar Also the directional arrows in the header logs should indicate where the responses are coming from Mainly you will be checking how often Zope Plone is handling requests the less often the

    Original URL path: http://www.enfoldsystems.com/software/proxy/docs/7.1/cachetutorial.html (2016-02-11)
    Open archived version from archive

  • Using Split Level Caching
    simultaneously There are several methods for solving this problem Enfold Proxy solves it by intercepting the request and dynamically adding a special X Anonymous header to the anonymous request and then adding Vary X Anonymous to the split view response so that this header will be added to the cache key Enabling split level caching in Plone The Plone caching add ons can allow your site to do split level caching Consult the add on s documentation for specific details Note after enabling it in Plone you will also need to add a line to the eep ini see below With the plone app caching add on available for Plone 4 activating and controlling split level caching is easy After installing this Plone add on the Plone administrator can activate and control split level caching via the plone app caching control panel in Plone Site Setup Plone app caching has two proxy profiles With caching proxy and With caching proxy and split view caching Selecting the second option will be sufficient Go to http plone org products plone app caching for more information In Plone 3 the caching add on CacheFu can do split level caching but it requires more manual configuration See the CacheFu documentation for details Enabling split level caching in a proxy definition For tips on how to configure the eep ini file see Configuring EP manually After you have configured split view caching with the Plone add on the next step is to add a line to the eep ini file For example if your proxy definition looks like this host myproxydefinition vh hosts 127 0 0 1 8080 vh root Plone lh root site 1 You should add this extra line for Proxy to support split level caching host myproxydefinition vh hosts 127 0 0

    Original URL path: http://www.enfoldsystems.com/software/proxy/docs/7.1/using-split-level.html (2016-02-11)
    Open archived version from archive

  • Purging Cache
    type in 2 IP addresses here First 127 0 0 1 which is localhost and second the actual IP address of your machine such as 192 168 1 1 If you are testing when logged on as a domain user on the machine itself sometimes IIS will treat domain requests as coming from outside the machine itself If you are unsure which IP address is making the PURGE request examine your IIS HTTP access logs and verify the IP address which made the PURGE request Special Note about Windows authentication NTLM and Purging Enfold Server ES lets you use NTLM authentication to automatically log users in If you are using NTLM with Enfold Server you might not be able to run purge commands successfully This is a known bug with Enfold Proxy 4 In Enfold Proxy EP there are four ways to purge the cache use the Purge button within Enfold Proxy recommended use the portal squid tool within the ZMI helpful for purging one specific URL only use a command line utility like cURL or Telnet to issue a PURGE command which the proxy server can understand for a specific URL do it from within a Plone add on include a Python script to purge cache content when an item is republished This topic will discuss the advantages and disadvantages of each method Purge Cache within Enfold Proxy Recommended Enfold Proxy includes a way to purge cache To do this select the Purge option on the left panel of EP s configuration utility By checking or unchecking each proxy definition you can delete the cache for one or multiple proxy definitions Purge a specific URL with Portal Cache Plone app caching or CacheFu lets you input a specific URL you wish to be cached Keep in mind that this URL will only cache a specific item So if you try to purge www originalfunsite com news it will not purge cache of jpegs or css files used on this web page Instead this request will purge only the contents of that page minus the css jpg gif js files To do this Confirm that the IP address of the requesting machine is explicitly listed in Enfold Proxy Settings Cache Purging Source If your IP address is not listed enter it now Go to the ZMI for your site and open the portal squid tool Located at Plone Site Setup Zope Management Interface portal squid in right panel near the bottom Follow the instructions for adding a Cache URL Press Save Example http www originalfunsite com In the field for Purge URL Enter the name of the web item relative to the Plone root Example logo jpg Logo jpg is a company logo jpeg that is found on the Plone home page Press Go Here are some responses you could conceivably receive after you press the Go button 404 http www originalfunsite com logo jpg Not cached 200 http originalfunsite com logo jpg Purged 401 http originalfunsite com logo jpg

    Original URL path: http://www.enfoldsystems.com/software/proxy/docs/7.1/purging.html (2016-02-11)
    Open archived version from archive

  • Cache Headers and Enfold Proxy
    Headers or Debug For more info see Headers log level Concepts The first time a person makes a request for a content item here is what typically happens At first Enfold Proxy does not have a cachable copy of the item so it must fetch it directly from Plone When an item is received from the backend server it is examined to see if it is cacheable that is if it is able to be stored in the cache and used to satisfy future requests for that item Unless Plone includes a special header which specifies that the item is not cacheable Enfold Proxy will keep a copy locally on its machine which it can use for responding to future browser requests If the sysadmin purges the cache for the proxy definition then all cached copies are deleted and Enfold Proxy has to start again from scratch After the initial request for a content item here is what typically happens When a client connects to EP and asks for a request EP first checks to see if it is in the cache that is if a previous request for the resource determined that it was cacheable as described above If the item is in the cache the next thing to be determined is if the item is stale A stale item means that although the item is in the cache the parameters for that item indicate that it is no longer allowed to be used directly If an item is fresh then it can be sent back to the client without contacting the backend server However if the item is stale EP can generally validate such items Validating an item consists of connecting to the server and asking the server if the version we fetched before is still the same If the server responds in the affirmative EP is still able to used the previously stale item and although contact was made with the back end server the data itself was not re transmitted It is important to understand the conceptual difference between an item being cachable and an item being fresh It is possible and quite common that a server will send a cachable response but indicate it is immediately stale i e by including a Max Age 0 or an Expires value which is already out of date This means that although EP can store the item in its cache it is not able to use it in client requests without first validating it with the server In this case the end result is that the cache will never serve old items because they are never fresh and require revalidation but bandwidth usage between EP and the backend server will be reduced because Plone won t need to send the content item itself only the 304 message with an updated date stamp HTTP Headers Reference There are a number of HTTP headers used to control caching Headers indicate if the response is cachable at all and if so

    Original URL path: http://www.enfoldsystems.com/software/proxy/docs/7.1/cacheheaders.html (2016-02-11)
    Open archived version from archive

  • XDV Tutorial
    makes it possible to use any pre existing design with a Plone back end The reason that this is exciting is that you re using your own HTML and CSS not modifying Plone s HTML and CSS How it Works A high level overview of what is going on in XDV The way XDV works is simple but since it might take a little adjustment of the mental model that you re used to if you have done theming in Plone or any other system it s worth an explanation The main difference is that you re not touching the templates and HTML from Plone itself at all Instead you create the layout and design you want in standalone HTML and CSS files and map parts of the content that comes out of Plone into your existing HTML This means that you can create as complex or simple designs as you want and let Plone supply the content This also means that you can write your own from scratch HTML and CSS but also map various Plone elements to wherever you want in your own design Plone knows nothing about what happens on the way out it just renders a page as it usually does A more visual way to look at it here you can see how the Plone output is mapped into a totally different template and design This makes for a much more robust approach to theming because as long as Plone keeps its HTML classes and IDs the same from one version to the next your theme will automatically work even in a new version of Plone And if it has changed it s a relatively simple operation to update the theme just locate the new name and replace it in the rule file The Rule File Central to the way that content makes its way from your Plone site into your theme is the rule file Let s look at your simple rule file again rules xmlns http namespaces plone org xdv Copy over the contents of the page body replace content id content theme id my content area rules Ignoring the preamble rules and the comment there s one single instruction here replace content id content theme id my content area So what does it do It looks at the Plone side of things content and locates the part of the HTML that has id content It then replaces the part of your theme s HTML that has id my content area with the content it got from Plone The syntax inside the content and theme attributes can be a bit intimidating luckily we have great tools to make it very easy to get this right The syntax is called XPath and is a standard for addressing nodes in the DOM and it s also directly supported in Firebug A full treatment of how Firebug works is out of scope for this tutorial but the Firebug online documentation should explain how to install it

    Original URL path: http://www.enfoldsystems.com/software/proxy/docs/7.1/xdvtutorial.html (2016-02-11)
    Open archived version from archive

  • Using EP With XDV Themes
    decide which theme to send back EP automatically compiles xdv themes and recompiles them whenever rules or theme file have changed You can apply different xdv themes to different urls Which theme is returned depends on whether the rules for the theme have been met This general example below shows how you can apply a theme for a URL depending on what header EP receives There are various reasons why you would want to serve a theme depending on the HTTP header One use case would be serving a different theme depending on whether the site visitor is an authenticated user or not EP xdv theme definition xdv theme name rules path to rules theme path to themes absolute prefix url absolute prefix reload true url URL regex1 URL regex2 URL regex3 headers HEADER NAME1 regexp1 HEADER NAME2 regexp2 HEADER NAME3 regexp3 rules path to xdv rules xml file theme path to xdv theme html file reload check if for modifications in rules and theme files in each request if these files are modified url apply theme to this urls url is regex Apply theme if any url is matched optional Empty url means apply to all urls headers list of header name header value regexp Apply theme if all headers match Optional Empty headers mean apply to all URLs absolute prefix The compiler can be passed an absolute prefix This is a string that will be prefixed to any relative URL for an image link or stylesheet in the theme HTML file before the theme is passed to the compiler This allows a theme to be written so that it can be opened and viewed standalone on the filesystem even if at runtime its static resources are going to be served from some other location Headers are keys in environment dictionary The environment dictionary logs to proxy log in debug log level See below Selecting a theme by not meeting a certain rule It is also possible to select themes based on not meeting a rule Let s look at that same example slightly modified xdv theme name rules path to rules theme path to themes absolute prefix reload true url URL regex1 URL regex2 URL regex3 headers HEADER NAME1 regexp1 HEADER NAME2 regexp2 HEADER NAME3 regexp3 Here the rules and theme options represent the paths to the XDV rules xml and theme xml files The reload option must be set to either true or false If reload is set to true then on each request Enfold Proxy checks for modifications to rules xml and theme xml and recompiles those files if necessary The url option is a list of regular expressions Enfold Proxy applies the XDV theme to any URL that matches any regular expression in this list An empty list means to apply the XDV theme to all requests regardless of URLs You can use char before each url this means NOT MATCH or apply theme to any url except this The headers option is a list

    Original URL path: http://www.enfoldsystems.com/software/proxy/docs/7.1/ep-xdv.html (2016-02-11)
    Open archived version from archive

  • Caching XSLT
    with all necessary files already fetched and parsed It is not a copy of what was received from a remote server it is an object in memory which represents the result of some XSLT processing It cannot be purged is unable to have items validated or have any setting overridden per style sheet The contents are lost when EP is stopped All options prefixed with object cache are referring to this cache Important Note XSLT caching is not currently supported on Windows Vista 64 bit Activate and Test XSLT Caching Because XSLT caching is an in memory cache instead of disk based cache the method for verifying that it works is less direct Unlike other cache hits XSLT caching will not give a X Cache HIT message in the host headers nor will it appear in the cache logs You will however be able to see a brief message confirming an xslt cache hit in the proxy log file It looks like this 2008 05 09 15 05 05 062 enfold lxml INFO 2076 3452 XSLT object cache hit for http localhost cdcatalog xsl 2008 05 09 15 05 05 108 enfold lxml INFO 2076 2460 XSLT object cache hit for http localhost cdcatalog xsl For this example you will add an XSL file into Zope so it is stored as an object and a python script which essentially outputs an XML file This example will put cdcatalog xml and cdcatalog xsl into the application root level of the ZMI Use the ZMI to add a python script which you will name cdcatalog xml Follow the same steps that you did for adding a Plone site From the Add dropdown menu in the ZMI select Script Python http localhost 8080 manage For ID type cdcatalog xml Press Save and Edit Copy this XML python script named cdcatalog xml into the edit box and press Save This python script causes a simple XML file to be outputted by Zope Note This is not actually an xml file but a python script to output XML Copy and paste the cdcatalog xsl file You can download the same file here http www w3schools com xsl cdcatalog xsl You might need to change the file extension so that it ends in xsl Use the ZMI to add this xsl file in the same directory as your python script Select File from the Add dropdown menu Give it id cdcatalog xsl and select Browse to find the file on your PC Be sure both objects are in the same directory and accessible The easiest way is to try to access http localhost cdcatalog xml and http localhost cdcatalog xsl Configure your Enfold Proxy settings by manually editing the eep ini file in your C Program Files Enfold Proxy directory Be sure to read the tips for manually editing the eep ini file Important You can enable XSLT caching only by manually editing the eep ini file Here is an example of how your eep ini

    Original URL path: http://www.enfoldsystems.com/software/proxy/docs/7.1/xslt.html (2016-02-11)
    Open archived version from archive



  •