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".
  • Managing Multiple Hosts
    ID from the eep ini file located in the Enfold Proxy directory and from the IIS management console Read more about unique identifier IDs and how to confirm that Enfold Proxy is reading them correctly near the bottom Creating a Second Internet Host and Proxy Definition For this example http www originalsite com is the first domain and http www funsite1 com is the second domain you will use Configure your first IIS host in the normal way See Configuring your first IIS host Verify that the first host resolves correctly See Verifying that the IIS Host resolves correctly Use IIS to create a new IIS site Right click on Web Sites within the IIS Manager and select New Web Site If using IIS 7 right click Sites and select Add Web Site Go through the IIS Site Creation wizard In this example the new site will be called funsite1 Notes you will need to indicate a directory for the site root You can simply use the default site root for IIS C Inetpub wwwroot or create one underneath this directory i e C Inetpub wwwroot The most important thing here is that the directory allows read access for the IIS user Enter Port Number 80 Host Header values www funsite1 com IP Address All Unassigned and leave allow anonymous access enabled Restart the Web Site You will not need to restart IIS itself In IIS 6 right click the site name funsite1 in the IIS Manager and choose Start or Restart In IIS 7 the Start Restart option is located on the right panel in the IIS Manager Highlight the funsite1 site in the middle panel and select the Start Restart option Test that your domain works in IIS See Verifying that the IIS Host resolves correctly Create a

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


  • How Caching Works
    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 the better To verify caching you will need to view your HTTP response headers Several browser tools let you do this Live HTTP Headers http livehttpheaders mozdev org is the recommended tool This is a Firefox plugin which lets you view http headers in real time For easier reading you can go to the Generator tab and filter out image requests Firebug http www getfirebug com Here is another Firefox plugin which not only records http headers for each item but also records other information like download speed You can view HTTP information for each HTTP request by clicking on the web resource Live HTTP Headers is probably better at capturing data in real time But Firebug shows graphically which resources on a web page are taking the longest time to load It is commonly assumed that dynamically generated server content accounts takes longer to load than images or scripts In fact Firebug reveals how often images and scripts are the culprits not the html content Fiddler http www fiddlertool com This is a tool for Internet Explorer A good MSDN tutorial about using fiddler is here http msdn2 microsoft com en us library bb250446 VS 85 aspx Tip 1 surf with two browsers More than likely you ll be using Firefox with Live Headers to inspect your http headers Then you can use one browser specifically to simulate a logged in user where different caching rules apply and the other browser to simulate the anonymous non logged in user where the most aggressive caching rules apply Tip 2 When you are logged in as administrative user a smaller percentage of your HTTP requests will be cached As a result response time for a Plone page might seem slower than they actually would appear to an anonymous user Interpreting HTTP Headers The next section covers how to read headers with the browser tools listed above However Enfold recommends examining EP logs directly instead of using browser tools whenever possible because they are less ambiguous and confusing Read more about how to view HTTP headers in the proxy log Ultimately the most accurate way to troubleshoot caching is to look at HTTP Headers This can be a daunting task Just one web page may involve 10 15 separate HTTP requests However if you have experience and know what to look for you can spot problems quickly without becoming bogged down For example a simple URL such as http www originalfunsite com events will consist of these requests GET events GET portal javascripts Enfold 20Theme ploneScripts6490 js GET portal css Enfold 20Theme ploneStyles6499 css GET portal css Enfold 20Theme ploneStyles1162 css GET portal css Enfold 20Theme ploneStyles6975 css GET favicon ico GET info icon

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

  • Caching with EP
    returning a particular Plone content type To do that go to the Rule tab and select the content type you want Each rule will let you specify a header for anonymous users and a rule for authenticated users Presumably you d want a reduced amount of caching for authenticated users The label for each header Do not Cache Cache in proxy cache for 1 hour Cache in browser for 1 hour etc should be self explanatory Keep in mind that you can also edit properties for each header on the Headers tab at the time of this writing January 2009 a browser bug in Internet Explorer prevents sysadmin users from viewing editing properties on the CachuFu Rules tab This bug does not affect users of Firefox As a result the hyperlinks on the CacheFu configuration page won t work properly you may need to open these hyperlinks in a new browser tab or browser window CMFSquidTool is an open source caching product supported by Enfold which lets you purge cache As long as you set your IP address in Caching Purge Sources see Purging Cache However you may find it easier to use Enfold Proxy to purge cached items for proxy definition s List of HTTP Headers supported by Enfold Proxy See the HTTP Header Reference Guide Enable Cache in your Proxy Definition By default when you create a proxy definition in EP caching is enabled However you might need to change your settings to suit your hardware See a description of each cache setting Enfold Proxy will keep a lot of stale cached files inside the cache directory corresponding to a specific proxy definition These stale cache files will accumulate in the cache directory until it approaches the maximum cache size That is actually a good thing In Chasseur for example a lot of content is cached for one hour After one hour or even after five years whenever the browser requests the same resource EP will check with Plone and ask is this stale item still valid Plone will give one of two responses Either Plone will reply it s still good In this case EP will return the stale item to the browser and update its own records to indicate that this stale cache is now valid This process is called revalidating the cache The HTTP headers to the user will say X Cache HIT from www originalfunsite com Plone will reply Nope That s an outdated version In this case Enfold Server or 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 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 In Chasseur the maximum age is Cache Control max age 3600 X Cache HIT from www originalfunsite com 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 The CacheFu Plone product for example offers a lot of fine grained controls and the ability to create caching rules Note if you suspect your cache settings are misconfigured purging your cache can often eliminate the problem See Purging Cache But EP also offers some cache settings to tweak Here are some default settings for each proxy definition as set by Enfold Proxy Maximum Size of the Cache 10 gigabytes for each proxy definition Maximum number of items in the cache for each proxy definition 50 000 Maximum size of an item which can be cached 100K Default Age 0 The main thing you can adjust here is storage amount and item size The larger the storage amount you have the more cacheable items EP can keep at

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

  • Purging Cache
    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 Portal cache is a product that comes installed by default on Enfold Server It also comes with the CacheFu suite of products This product visible in the ZMI but not Plone 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 portal squid 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 Unauthorized this happens if you are trying to purge when IIS is using NTLM See note above Using cURL for purging cURL http curl haxx se docs manual html is a command line tool for making HTTP requests With cURL you can make the purge request for a specific URL rather than making a global command Just use the command curl X PURGE http host port path to url to be purged This tool is useful for testing and troubleshooting However if you are using a different machine make sure that its IP address you are using to run cURL is listed as a safe address in the Caching Purge Sources field under Settings in EP s configuration utility The PURGEALL command allows you to remove all items in the cache or all items that start with the specified string or if you specify the root of the EP site all items in the cache For example curl X PURGEALL http localhost would remove all cached items assuming vh root is set to point to the root of the IIS site Also note that specifying the v option to cURL will show more information

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

  • Cache Headers: Concepts & Strategies
    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 cachable 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 cachable 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 The goal is to maximize the number of items EP can send back to the browser without having to consult Plone Enfold Server 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 EP needs to determine if the item is stale A stale item means that although the item is in the cache parameters for that item indicate that it is no longer allowed to be used directly If an item is fresh 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 Plone and asking if the version fetched before is still the same If the server responds in the affirmative EP is still able to used the previously stale item 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 EP can t use it in client requests without first validating it with Plone In this case EP will never serve old cached items because they are never fresh and require revalidation Still having Plone send a cachable but stale response will reduce bandwidth usage between EP and Plone because Plone won t need to send the content item itself only the 304 message with an updated date stamp Which headers does EP support A number of HTTP headers are used to control caching Headers indicate if the response is cachable at all and

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

  • Caching XSLT
    by the proxied server All options prefixed with cache are referring to this cache An in memory cache of style sheets This cache stores a fully processed style sheet tree 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 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

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

  • EP Interface Guide
    you must include it in the value Cache Options See also Configuring Cache with Enfold Proxy and Caching Goals and Strategies Note about configuring these options manually All the cache options for a particular host section are set directly in that host section inside the eep ini file In eep ini each host section corresponds with a proxy definition All cache related configuration options are prefixed with cache User interface Configuration file Default Description Cache enabled cache enabled True Indicates if caching should be enabled Cache directory cache directory Leaving it blank will put cache directory inside Program Files Enfold Proxy cache directory If you change you must use an absolute paths i e C My Documents cache See the cache directory for more information Default age for items cache default age 0 For content without explicit expiry information how long in seconds should the page be considered fresh If this is not zero EP will cache everything for at least that duration even data that is updated frequently Maximum size of cache cache max size 100000000 The maximum size of the cache in bytes This size may temporarily be exceeded depending on the transient load factor option Maximum item size cache max item size 200000 The maximum size of an item that will be cached Items larger than this will not be stored Note that when items bound for the cache are read from the remote host they will be buffered in memory so this value will affect memory usage Transient load factor cache transient load factor 1 2 The factor by which the cache may temporarily exceed max size until the cache scavenger reduces it back This is to avoid a client connection taking the penalty of cache expiry if the cache is full Scavange delay cache scavenge delay 60 How often the cache scavenger runs The cache scavenger will reduce the cache back down to max size and flush the cache index to disk Cache other response allow non 200 False Enables caching of responses other than 200 such as redirects 301 302 and not founds 404 if such responses have appropriate cache headers Object Cache Options These options modify the in memory cache used by the XSLT processing as described in XSLT caching You cannot enable these options with the EP Configuration Tool instead you need to add the options by manually configuring the eep ini file Configuration file Default Description object cache enabled False Is the object cache enabled object cache max len 50 Number of items in the cache object cache default age 600 10 mins Length of time these items are cached object cache log level WARNING The level of logging messages generated by this cache The log messages are currently sent to the main proxy log ZEO and Load Balancing options See also Configuring Load Balancing Enfold Proxy has the ability to balance requests between any number of hosts It is assumed that all these hosts are identical Plone installations using a

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

  • Configuring EP Manually
    Remember that if you only use the EP configuration tool this information will not apply Tips for Editing the eep ini file Vista Users Vista s security model is intended to prevent the user from accidentally writing editing system or configuration files The Encontrol configuration utility will automatically prompt for the necessary elevation of privileges but if you wish to edit this file by hand you will need to do so from a process that is already elevated ie started with Run as Administrator see the Vista documention about how to do that In order to use the configuration file directly go to Start Enfold Proxy Configuration File This file can be edited with any text editor and is laid out like any other Windows INI file Throughout this documentation this image is used to highlight instructions for editing the configuration file Don t forget If you edit eep ini manually you must run eep exe afterwards If you do not your edits may not take effect Most settings are insensitive to case but lines should begin in the left column i e have no leading whitespace unless they are part of a line continuation see section below Except where noted all settings can be changed without restarting IIS however the new options will not be processed until a connection is made to Enfold Proxy If you make a configuration change you should visit the proxy in your browser to ensure the changes have taken effect as expected If your site configuration is quite complex such that your INI file becomes difficult to manage be sure to read the documentation on using variables in configuration files Continuing Long Lines If you maintain the configuration file in a text editor rather than via the UI utility it is possible to split configuration values over multiple lines Simply continue the value on the next line but ensure that line begins with at least one space or tab For example host 1 includes file1 file2 file3 file4 file5 Note that the UI utility may merge the multiple lines back into one when saving Using Variables in Configuration Files Enfold s INI files have a feature that make setting up large configuration files quite simple you can define variables in the INI file and can then refer to these variables in the configuration values In the simplest example let assume you had a large number of excludes to specify One way of doing this is as follows host something jpg files foo jpg bar jpg css files logo css myapp css excludes jpg files s css files s In this example we have defined 2 variables jpg files and css files As these variable names to not match any configuration options used by EP they have no effect on EP itself excludes is an EP option and its value is defined as being the concatenation of 2 variables This is equivalent to as if the configuration file had read host something excludes foo jpg

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



  •