Version 7.1 (June, 2011)

New features include:

• Support caching of HTTP/1.0 requests.

Fixes:

• Fixed logging for proxy extensions.
• Fixed bug that could cause the Zope homepage to display instead of the homepage for the Plone site.

Version 7.0 (December, 2010)

New features include:

• Full Support for the etag and vary HTTP headers.
• 64 bit versions of Enfold Proxy (EP) now support XDV/XSLT Caching.
• EP now supports "split view" caching. This allows EP to use different caching methods for different parts of the same page. This can be helpful in caching components of a web page for logged in users. Read more about split-level caching.
• Works with Plone 3 and 4 and with plone.app.caching add-on.

Fixes:

• The ordering of the proxy definitions in the ep.ini file no longer affects how or whether EP will process them. You can optionally use excludes_regex for more fine-grained control over which proxy definition acts upon a particular URL.
• EP will not store requests which were initially found to be invalid.

Version 6.1 (September, 2010)

New features include:

• Added an option in the EP configuration tool to disable one or more proxy definitions temporarily.
• More support for XDV theming. Added a way to select a theme by not meeting a certain rule (more).
• Added documentation for developers about more complex configurations of XDV themes. That includes: Selecting a theme based on URLs and/or HTTP headers.
• Added the absolute prefix field to XDV definitions. This field allows EP to rewrite relative URLs.
• Added options which will specify actions to take in response to 500 messages. (Read more about 500 messages).

Version 6.0 (May, 2010)

New features include:

• Added ability to provide policy over how load balancing schedulers route requests.
• Implemented XDV theming. For more information, see the XDV tutorial.

Bug fixes:

• When a remote host closed its connection, Enfold Proxy now correctly detects prematurely closed socket.

Other notes:

• Do not use rewrite feature of IIS 7 site if Enfold Proxy is being used on the site.

Version 5.2 (March, 2010)

• Added an error message if you try to install Enfold Proxy when IIS is not running. When installing, IIS must be running for the installation to be configured correctly. This error message will appear if you run the Check function on the Enfold Proxy configuration panel (or the equivalent command line utility).
• Fixed a bug that sometimes caused a discrepancy between the proxy definitions appearing in the EP configuration panel and the proxy definitions appearing in the eep.ini configuration file.
• Removed duplicate words in the cache headers.
• Added a warning message if you include a value for vh_server and vh_hosts in eep.ini. (vh_hosts is for load balancing while vh_server is not. They should not be used together). This warning message will appear if you run the Check function on the Enfold Proxy configuration panel (or the equivalent command line utility).

Version 5.1 (November, 2009)

• Fixed bug that caused Enfold Proxy (EP) to merge multiple cookies, with the same "expire" value applied to both cookies.
• Added updated documentation including a section on cache headers and caching strategies.

Version 5.0 (July, 2009)

New features include:

• Enfold Proxy has been rearchitected to use WSGI.
• Enfold Proxy now supports caching responses other than 200. Meaning Redirects, Not Found and other HTTP responses can be cached.
• Windows Installer now detects the version of Windows directs web browser to the correct instruction based on Windows version
• Enfold Proxy configuration checking tool (eep_check.exe) is stricter and provides better feedback.
• Enfold Proxy configuration utility now has a support tab that will automatically zip all log files and place them on the users desktop

Other improvements and changes:

• Enfold Proxy 5 now requires IIS 6 or higher. Windows XP, Windows 2000 or earlier are no longer supported. Windows 2003, Vista and Windows 2008 are supported.
• X-Cache-Hit accurately reflects the age of a cached item.
• Bug in encontrol which resulted in MAX. Log rollover size to not be written correctly to configuration file.
• Connection: response header may have "Close, Close" as value; this is no longer possible.
• Increase the default timeout for remote server from 90 seconds to 180 seconds
• There are no longer _Plone virtual directory created in the IIS Manager
• Proxy log analyzer tool improvements, check --help

Version 4.7 (April, 2009)

• Cache storage had a possibility of having different date representations which could reduce effectiveness of cache.
• Improvements around IIS worker process recycling.
• Removed asynchronous logging capability which could generate incorrect logs.
• Fixed a race condition which could cause EP to become unresponsive upon IIS startup.
• Added a eep.ini configuration for thread_pool_shutdown_timeout.

Version 4.6 (January, 2009)

• Enfold Proxy will no longer attempt to 'prime' the EP cache by modifying incoming client requests; in certain cases, doing so led to poor performance. EP will not store an item in cache until the first non-conditional request for that page comes from a client.
• Minor tweaks to the wording on encontrol, error messages and docs.
• Documented a method for making 64 bit EP run in 32 bit mode.

List of Known Issues

• When upgrading, you should stop IIS via the command line instead of doing it with the IIS configuration tool. Otherwise errors may occur. Read more.

Searching through current & resolved issues

Enfold keeps a "collector" of ongoing issues related to products. (If you bought a subscription, you will have a login for the Priority Enfold Proxy Collector at https://entrack.enfoldsystems.com/browse/PROXYSUP). This not only lets you create issues of your own, it also allows you to view issues created by other clients as well.

There are two ways to browse through the Priority Proxy collector:

1. Enter a specific term or phrase in the Search box at the top.
2. Click one of the links under Project Summary or Open Issues on the right side. If browsing in this way, don't forget to browse through the Closed issues. Not only are there far more closed issues than open ones, but the closed issues often include solutions and advice from Enfold's technical support staff and sometimes even from developers.