Quick Pic 2.1.0 serial key or number

Installazione

Requisiti minimi

• WordPress 5.0
• WooCommerce 3.0 and later.
• PHP version 7.0 or greater
• MySQL version 5.6 or greater

Installazione automatica

Automatic installation is the easiest option as WordPress handles the file transfers itself and you don’t even need to leave your web browser. To do an automatic install of Products Quick View, log in to your WordPress admin panel, navigate to the Plugins menu and click Add New. Search Products Quick View for WooCommerce and click install. Or download the plugin from wordpress.org and click the upload sub nav item and use the WordPress plugins uploader to upload the plugin from your computer and unpack it and install it for you.

Installazione manuale

The manual installation method involves downloading our plugin and uploading it to your web server via your favourite FTP application.

1. Download the plugin file to your computer and unzip it
2. Using an FTP program, or your hosting control panel, upload the unzipped plugin folder to your WordPress installations wp-content/plugins/ directory.
3. Activate the plugin from the Plugins menu within the WordPress admin.

FAQ

When can I use this plugin?

On any WordPress install that has the WooCommerce plugin installed and activated.

Recensioni

this allowed me to prop up a quick auction page (using simple auctions) and have a popup window for item bidding in popup without user leaving archive page. Great solution for this. Appreciate the hard work you had setting up. cheer. Vince.

If I upload 10 images to a product, but do not add them to the gallery, or anywhere else in the post, these still show in the slideshow - not ideal as I sometimes upload masses of photos on a product for use elsewhere later. Out of the box styling needs modifying to display nicely. It's a good idea, but needs to be refined to inherit styles from the theme. I'd rather run without it at this stage.

Hi, enfold theme, TM Global Product options, all variables are done via this plugin, simple product in woo. (Think a framed picture, you select image, variables are framing mounting etc) I can find ANY setup where the product is opened into the popup. Always being sent back to the product page that I want to avoid. Any idea please?

Worked very well on my website..This is for sure one of the best plugin in the wp repository

The free version, used as a test before purchase, does not work at all. Shows no quick view images or content. Just pops up an empty white window. Seems worthless unless the developer can actually make a working piece of software. Waste of time.

Changelog (registro delle modifiche)

1.9.3 – 2020/08/08

• This maintenance release is for compatibility with WordPress major version 5.5 and WooCommerce 4.3.1.
• Tweak – Test for compatibility with WordPress 5.5
• Tweak – Test for compatibility with WooCommerce 4.3.1

1.9.2 – 2020/07/14

• This maintenance release has a fix for Fatal Error when product variations do not have a price entered, plus compatibility with WooCommerce 4.3 and WordPress 5.4.2
• Tweak – Test for compatibility with WooCommerce v 4.3.0 and add tested tag
• Tweak – Test for compatibility with WordPress 5.4.2
• Fix – Validate product is correct object before called member functions

1.9.1 – 2020/04/01

• This maintenance release is for compatibility with WordPress 5.4, WooCommerce 4.0.1, Travis CI build unit test for compliance with WordPress PHP coding standards and PHP tweaks for compatibility with PHP v 7.0 to 7.4
• Tweak – Test for compatibility with WordPress 5.4
• Tweak – Test for compatibility with WooCommerce 4.0.1
• Tweak – Plugin Framework fully refactored to Composer for cleaner code and faster PHP code on admin panels
• Tweak – Update plugin for compatibility with new version of plugin Framework
• Fix – Update global ${$option to $GLOBALS[$option to resolve 7.0+ PHP warnings
• Fix – Update less PHP lib that use square brackets [] instead of curly braces {} for Array, depreciated in PHP 7.4
• Fix – Validate to not use get_magic_quotes_gpc function that are depreciated in PHP 7.4

1.9.0 – 2019/12/20

• This feature release upgrades the plugins PHP to Composer Dependency Manager, a full security review plus compatibility with WordPress 5.3.0 and WooCommerce 3.8.1
• Feature – Plugin fully refactored to Composer for cleaner and faster PHP code
• Tweak – Remove the hard coded PHP error_reporting display errors false from compile sass to css
• Tweak – Test for compatibility with WordPress 5.3.0
• Tweak – Test for compatibility with WooCommerce 3.8.1
• Dev – Replace file_get_contents with HTTP API wp_remote_get
• Dev – Ensure that all inputs are sanitized and all outputs are escaped

1.8.8 – 2019/09/03

• This upgrade is for compatibility with Responsi Framework 7.6.0 and WooCommerce 3.7.0
• Refactor – Rewrite frontend HTML, CSS, JS and Variables Class and ID names to the new framework 7.6.0 namespaces
• Refactor – Rewrite customizer HTML, CSS, JS and Variables Class and ID names to the new framework 7.6.0 namespaces
• Refactor – HTML, CSS, JS and Variables Class and ID names called from the framework making plugin file sizes smaller and faster to load
• Tweak – Test for compatibility with WooCommerce 3.7.0

1.8.7 – 2019/06/29

• This is a maintenance upgrade to fix a potentially fatal error conflict with sites running PHP 7.3 plus compatibility with WordPress v 5.2.2 and WooCommerce 3.6.4
• Tweak – Test for compatibility with WooCommerce 3.6.4
• Tweak – Test for compatibility with WordPress 5.2.2
• Fix – PHP warning continue targeting switch is equivalent to break for compatibility on PHP 7.3

1.8.6 – 2019/04/26

• This maintenance update has tweaks for compatibility with WordPress 5.2.0 and WooCommerce 3.6.0 major new versions whilst maintaining backward compatibility
• Tweak – Test for compatibility with WordPress 5.2.0
• Tweak – Test for compatibility with WooCommerce 3.6.2
• Tweak – Support for backward compatibility with WooCommerce v 3.5

1.8.5 – 2018/12/27

• This maintenance update is for compatibility with WordPress 5.0.2, WooCommerce 3.5.3 and PHP 7.3. It also includes performance updates to the plugin framework.
• Tweak – Test for compatibility with WordPress 5.0.2 and WordPress 4.9.9
• Tweak – Test for compatibility with WooCommerce 3.5.3
• Tweak – Create new structure for future development of Gutenberg Blocks
• Framework – Performance improvement. Replace wp_remote_fopen with file_get_contents for get web fonts
• Framework – Performance improvement. Define new variable if admin does not require to load google fonts
• Credit – Props to Derek for alerting us to the framework google fonts performance issue
• Framework – Register style name for dynamic style of plugin for use with Gutenberg block
• Framework – Update Modal script and style to version 4.1.1
• Framework – Update a3rev Plugin Framework to version 2.1.0
• Framework – Test and update for compatibility with PHP 7.3

1.8.4 – 2018/05/26

• This maintenance update is for compatibility with WordPress 4.9.6 and WooCommerce 3.4.0 and the new GDPR compliance requirements for users in the EU
• Tweak – Test for compatibility with WooCommerce 3.4.0
• Tweak – Test for compatibility with WordPress 4.9.6
• Tweak – Check for any issues with GDPR compliance. None Found
• Framework – Update a3rev Plugin Framework to version 2.0.3

1.8.3 – 2018/02/13

• Maintenance Update. Under the bonnet tweaks to keep your plugin running smoothly and is the foundation for new features to be developed this year
• Framework – Update a3rev Plugin Framework to version 2.0.2
• Framework – Add Framework version for all style and script files
• Tweak – Update for full compatibility with a3rev Dashboard plugin
• Tweak – Test for compatibility with WordPress 4.9.4
• Tweak – Test for compatibility with WooCommerce 3.3.1

1.8.2 – 2018/01/24

• Maintenance Update. 1 bug fix for conflict with 3rd party plugin pop ups.
• Tweak – Tested for compatibility with WordPress 4.9.2
• Fix – Check if pp_overlay is appended to document before allow 3rd party plugin call to trigger quick_view_close_popup

1.8.1 – 2018/01/15

• Maintenance Update. This version has 1 major code tweak and 1 bug fix with the prettyPhoto pop up script.
• Tweak – Load prettyPhoto script from plugin. Was previously loaded from the WooCommerce plugin but it was depreciated from their gallery – now use Zoom lib which is not a pop up.
• Fix – Load script with correct order to resolve the JavaScript prettyPhoto is not defined error
• Credit – Thanks to Ignacio Cano for reporting the bug.

1.8.0 – 2017/12/19

• Feature upgrade. Added full support for WooCommerce default product gallery including zoom feature and variation images
• Tweak – Remove Dynamic Gallery script
• Tweak – Remove Dynamic Gallery Tab and setting options
• Tweak – Remove depreciated Fancybox option for popup tool. Automatically set to PrettyPhoto if site was using the Fancybox pop up
• Tweak – Tested for compatibility with WooCommerce 3.2.6
• Tweak – Tested for compatibility with WordPress 4.9.1

1.7.2 – 2017/10/13

• Tweak – Tested for compatibility with WooCommerce 3.2.0
• Tweak – Tested for compatibility with WordPress 4.8.2
• Tweak – Added support for the new WC ‘tested up to’ feature to show this plugin has been tested compatible with WC updates

1.7.1 – 2017/07/01

• Tweak – Tested for full compatibility with WooCommerce version 3.1.0
• Tweak – Show warning for variation is unavailable on popup
• Tweak – Set add to cart button to disabled if variation is unavailable on popup
• Fix – Show the Reset link on popup if Variable Product has default attributes

1.7.0 – 2017/06/07

• Feature – Launched WooCommerce Products Quick View public Github Repository
• Tweak – Tested for compatibility with WordPress major version 4.8.0
• Tweak – tested for compatibility with WooCommerce version 3.0.7
• Tweak – WordPress Translation activation. Add text domain declaration in file header
• Tweak – Include bootstrap modal script into plugin framework
• Tweak – Update a3rev plugin framework to latest version

1.6.1 – 2017/04/25

• Tweak – Tested for full compatibility with WooCommerce version 3.0.4
• Tweak – Tested for full compatibility with WordPress version 4.7.4
• Tweak – Change call direct to Product properties with new function that are defined on WC v3.0
• Tweak – Use new wc_get_product_category_list() function instead of product-get_categories() for compatibility with WC 3.0
• Tweak – Use new wc_get_product_tag_list() function instead of product-get_tags() for compatibility with WC 3.0
• Tweak – Use new get_gallery_image_ids() function instead get_gallery_attachment_ids() for compatibility with WC 3.0
• Tweak – Set better height for PrettyPhoto popup
• Fix – PrettyPhoto pop up can load full content on popup

1.6.0 – 2017/02/14

• Feature – Add PrettyPhoto Pop up Tool option for Quick View
• Tweak – Update Quick View script to support PrettyPhoto popup tool
• Tweak – Increase maximum Pop up maximum width option to 1000px and change default value to 800px
• Tweak – Added full compatibility with X theme.
• Tweak – Added full compatibility with WooCommerce Carousel & Slider plugin.
• Tweak – Depreciated FancyBox pop up tool
• Tweak – Added notice not to use FancBox pop up as it will be removed in future version
• Tweak – Change global $$variable to global ${$variable} for compatibility with PHP 7.0
• Tweak – Update a3 Revolution to a3rev Software on plugins description
• Tweak – Added Settings link to plugins description on plugins menu
• Tweak – Tested for full compatibility with WordPress version 4.7.2
• Tweak – Tested for full compatibility with WooCommerce version 2.6.14

1.5.1 – 2016/10/22

• Tweak – Tested for full compatibility with WooCommerce version 2.6.6
• Fix – Update add-to-cart-variation.js script for variation product when add to cart

1.5.0 – 2016/09/03

• Feature – Plugin Framework Mobile First focus upgrade
• Feature – Massive improvement in admin UI and UX in PC, tablet and mobile browsers
• Feature – Introducing opening and closing Options Boxes on admin panels
• Feature – Added Font editor ‘Line Height’ option
• Feature – Support select Default Gallery of WC or Dynamic Gallery show on Quick View Pop-up
• Feature – Upgrade all Gallery and thumbnail slider images to fontawesome icons
• Feature – Add colorbox pop up tool option
• Feature – Add customization options for fancybox and colorbox pop up tools
• Tweak – Change Pop-up Controls to font awesome icon
• Tweak – Move Plugin menu to as submenu of WooCommerce menu
• Tweak – Update select type of plugin framework for support group options
• Tweak – Update Typography Preview script for apply ‘Line Height’ value to Preview box
• Tweak – Update the generate_font_css() function with new ‘Line Height’ option
• Tweak – Replace all hard code for line-height inside custom style by new dynamic ‘Line Height’ value
• Tweak – Register fontawesome in plugin framework with style name is ‘font-awesome-styles’
• Tweak – Update a3 Dynamic Gallery script and style to support new features
• Tweak – Update dynamic style for new features
• Tweak – Tested for full compatibility with WooCommerce version 2.6.4
• Tweak – Tested for full compatibility with WordPress version 4.6

1.4.1 – 2016/06/21

• Tweak – Enqueue scripts to ‘wp_enqueue_scripts’ instead of footer to resolve script can’t load if theme don’t have wp_footer
• Tweak – Register two new scripts ‘quick-view-hover-script’ and ‘quick-view-popup-script’
• Tweak – Tested for full compatibility with WooCommerce major version 2.6.0
• Tweak – Tested for full compatibility with WooCommerce version 2.6.1
• Tweak – Tested for full compatibility with WordPtress version 4.5.2
• Fix – update minus and plus script for just increase 1 time for when click instead of increase 2 or 3 times
• Fix – Add to cart works on quick view pop up for Variation product that have custom attributes
• Fix – Update style to not have padding when Quick View hover type is activated

1.4.0 – 2016/04/11

• Feature – Completed full integration with WooCommerce Product Image Gallery. Dynamic Gallery functions and features are now applied to WooCommerce Product Gallery and does not create its own Gallery
• Tweak – Define new ‘strip_methods’ argument for Uploader type, allow strip http/https or no
• Tweak – Register fontawesome in plugin framework with style name is ‘font-awesome-styles’
• Tweak – Update a3 Dynamic Gallery script and style to support new feature
• Tweak – Saved the time number into database for one time customize style and Save change on the Plugin Settings
• Tweak – Replace version number by time number for dynamic style file are generated by Sass to solve the issue get cache file on CDN server
• Tweak – Update plugin framework to latest version
• Tweak – Tested for full compatibility with WordPress major version 4.5
• Tweak – Tested for full compatibility with WooCommerce version 2.5.5
• Dev – Add ‘quick_view_product_sku’ selector class for SKU meta on popup
• Dev – Add ‘quick_view_product_category’ selector class for Product Categories meta on popup
• Dev – Add ‘quick_view_product_tag’ selector class for Product Tags meta on popup
• Fix – Update Dynamic script to get data from attributes of gallery container instead of using ‘a3_dgallery_arg’ variable to parse into script. Resolves confliction with WooCommerce Dynamic Gallery plugin
• Fix – Remove ‘z-index’ for Control Bar. Now obsolete with Dynamic gallery html structure. Resolves conflict with any overlaying html for example from sidebar navigation pop out menus
• Fix – Remove ‘parseInt’ javascript function that was applying to get thumbnail type. Was causing the thumbnail container UI to be broken
• Fix – Support shortcode for the description on Custom Quick View Popup
• Credit – Thanks to Lana Mangusa for the suggestion to add sku, category and tag CSS selector classes for developers a3rev.com/forums/topic/quick-view-product-meta/

1.3.0 – 2016/01/29

• Feature – Add new popup content Feature – Simple Custom Template
• Feature – Custom Template has Dynamic gallery feature in popup
• Feature – Make Dynamic Gallery on frontend support the Responsive Image with 2 new attribute ‘scrset’ and ‘sizes’ are put on thumbnail and main image for decrease the total size of images are load on gallery for small screen
• Feature – Change old Media Uploader pop-up to New UI of Uploader with Backbone and Underscore from WordPress
• Feature – Added full support for Right to Left RTL layout on plugins admin dashboard
• Feature – Added Option to set Google Fonts API key to directly access latest fonts and font updates from Google
• Feature – Custom Template – Thumbnails use Hard Crop or Scale set on the WooCommerce Product Images settings
• Feature – Define new function – hextorgb() – for convert hex color to rgb color on plugin framework
• Feature – Define new function – generate_background_color_css() – for export background style code on plugin framework that is used to make custom style
• Tweak – Remove Pop up Content type, Product Page Content Feature – has been replaced by the Simple Custom Template feature
• Tweak – Update the uploader script to save the Attachment ID and work with New Uploader
• Tweak – Change call action from ‘wp_head’ to ‘wp_enqueue_scripts’ and use ‘wp_enqueue_style’ function to load style for better compatibility with minify feature of caching plugins
• Tweak – Change call action from ‘wp_head’ to ‘wp_enqueue_scripts’ to load google fonts
• Tweak – Updated a3 Plugin Framework to the latest version
• Tweak – Defined ‘frontend_register_scripts’ function with all gallery scripts are registered here for easy to enqueue on frontend
• Tweak – Move all upgrade function code to /includes/updates/ path
• Tweak – Update the frontend process for get new gallery of product
• Tweak – Update core style and script of plugin framework for support Background Color type
• Tweak – Updated required WordPress version to 4.1 for full compatibility with WooCommerce plugin
• Tweak – Tested for full compatibility with WooCommerce version 2.5.1
• Tweak – Tested for full compatibility with WordPress version 4.4.1
• Fix – Quick View feature work for when use WooCommerce shortcode on homepage or any page or when it’s related products, current it just work for shop page

1.2.5 – 2015/08/19

• Tweak – Tested for full compatibility with WooCommerce Version 2.4.4
• Tweak – Tested for full compatibility with WordPress major version 4.3.0
• Tweak – Include new CSSMin lib from https://github.com/tubalmartin/YUI-CSS-compressor-PHP-port into plugin framework instead of old CSSMin lib from http://code.google.com/p/cssmin/ , to avoid conflict with plugins or themes that have CSSMin lib
• Tweak – Make __construct() function for ‘Compile_Less_Sass’ class instead of using a method with the same name as the class for compatibility on WP 4.3 and is deprecated on PHP4
• Tweak – Change class name from ‘lessc’ to ‘a3_lessc’ so that it does not conflict with plugins or themes that have another Lessc lib
• Fix – Check ‘request_filesystem_credentials’ function, if it does not exists then require the core php lib file from WP where it is defined
• Fix – Make __construct() function for ‘WC_Quick_View_Ultimate’ class instead of using a method with the same name as the class for compatibility on WP 4.3 and is deprecated on PHP4
• Fix – Make __construct() function for ‘WC_Quick_View_Ultimate_Style’ class instead of using a method with the same name as the class for compatibility on WP 4.3 and is deprecated on PHP4

1.2.4 – 2015/06/04

• Tweak – Tested for full compatibility with WooCommerce Version 2.3.10
• Tweak – Tested for full compatibility with WordPress Version 4.2.2
• Tweak – Security Hardening. Removed all php file_put_contents functions in the plugin framework and replace with the WP_Filesystem API
• Tweak – Security Hardening. Removed all php file_get_contents functions in the plugin framework and replace with the WP_Filesystem API
• Fix – Update dynamic stylesheet url in uploads folder to the format so it’s always is correct when loaded as http or https

1.2.3 – 2015/05/05

• Tweak – Tested for full compatibility with WordPress Version 4.2.1
• Fix – Removed check_ajax_referer() call on frontend for compatibility with PHP caching plugins. Was returning -1 to js success call-back.

1.2.2 – 2015/04/21

• Tweak – Tested and Tweaked for full compatibility with WordPress Version 4.2.0
• Tweak – Tested and Tweaked for full compatibility with WooCommerce Version 2.3.8
• Tweak – Update style of plugin framework. Removed the [data-icon] selector to prevent conflict with other plugins that have font awesome icons

1.2.1 – 2015/03/19

• Tweak – Tested and Tweaked for full compatibility with WooCommerce Version 2.3.7
• Tweak – Tested and Tweaked for full compatibility with WordPress Version 4.1.1

1.2.0 – 2015/02/13

• Tweak – Maintenance update for full compatibility with WooCommerce major version release 2.3.0 with backward compatibility to WC 2.2.0
• Tweak – Tested fully compatible with WooCommerce just released version 2.3.3
• Tweak – Changed WP_CONTENT_DIR to WP_PLUGIN_DIR. When an admin sets a custom WordPress file structure then it can get the correct path of plugin
• Tweak – Added Link to new plugins a3 Lazy Load and a3 Portfolio to the Free WordPress plugins list in yelow sidebar.
• Tweak – Tested 100% compatible with WordPress Version 4.1
• Fix – Sass compile path not saving on windows xampp

1.1.1 – 2014/09/12

• Tweak – Tested 100% compatible with WooCommerce 2.2.2
• Fix – Changed DIR to dirname( FILE ) for Sass script so that on some server __DIR___ is not defined

1.1.0 – 2014/09/05

• Feature – Converted all front end CSS #dynamic {stylesheets} to Sass #dynamic {stylesheets} for faster loading.
• Feature – Convert all back end CSS to Sass.
• Tweak – use wc_get_product() function instead of get_product() function when site is using WooCommerce Version 2.2
• Tweak – Updated google font face in plugin framework.
• Tweak – Tested 100% compatible with WooCommerce Version 2.2 and backward to Version 2.1
• Tweak – Tested 100% compatible with WordPress Version 4.0

1.0.6.4 – 2014/06/19

• Tweak – change wp_register_script( ‘a3rev-chosen’) to wp_register_script( ‘a3rev-chosen-new’)
• Tweak – Tested 100% compatible with WooCommerce version 2.1.11

1.0.6.3 – 2014/06/04

• Tweak – Updated chosen js script to latest version 1.1.0 on the a3rev Plugin Framework
• Tweak – Tested fully compatible with WooCommerce Version 2.1.10

1.0.6.2 – 2014/05/29

• Tweak – Update change_button_text() function from ( $original == ‘Insert into Post’ ) to ( is_admin() && $original === ‘Insert into Post’ )
• Tweak – Added support for placeholder feature for input, email , password , text area types.

1.0.6.1 – 2014/05/19

• Tweak – Updated Pop-up menu with new Pro Version features set custom pop-up width and height.
• Tweak – Updated Custom Template, Product Data > Product Description menu with new Pro Version features.
• Fix – Quick View Fancybox pop-up menu not scrolling in iOS Mobiles

1.0.6 – 2014/05/17

• Feature – Added option to show Quick View button or link text under image
• Feature – Added full Quick View Button customization with the a3rev Button Creator functions – Create any style button.
• Feature – Added Button transparency setting for Quick View hover button.
• Feature – Added Under Image Button creator and Hyperlink styling functions.
• Tweak – Moved the plugin from a sub menu item on the WooCommerce menu to its own WordPress Admin menu WC Quick View.
• Tweak – Added all Custom Template Menus as a Sub menu of WC Quick View (Pro Version new feature)
• Tweak – Updated the plugins description text with new features for Lite and Pro versions.
• Tweak – Updated the plugins admin help text and yellow sidebar content.
• Tweak – Tested 100% compatible with WooCommerce Version 2.1.9

1.0.5.1 – 2014/05/12

• Tweak – Updated Framework help text font for consistency.
• Tweak – Added remove_all_filters(‘mce_external_plugins’); before call to wp_editor to remove extension scripts from other plugins.
• Tweak – Launched Plugin Pro Version Trail License for Free Trail.
• Tweak – Updated the plugins admin panel Yellow sidebar content.
• Tweak – Update plugins description text for easier reading.
• Tweak – Tested for full compatibility with WooCommerce Version 2.1.8
• Tweak – Tested for full compatibility with WordPress Version 3.9.1

1.0.5 – 2014/01/28

• Feature – Upgraded for 100% compatibility with soon to be released WooCommerce Version 2.1 with backward compatibility to Version 2.0
• Feature – Added all required code so plugin can work with WooCommerce Version 2.1 refactored code.
• Tweak – Removed dynamic pop-up wide setting and replaced with static pop-up max wide.
• Tweak – Pop-up tools wide under 520px shows 100% wide of the screen for mobiles in portrait or landscape
• Tweak – Added description text to the top of each Pro Version yellow border section
• Tweak – Tested for compatibility with WordPress version 3.8.1
• Tweak – Full WP_DEBUG ran, all uncaught exceptions, errors, warnings, notices and php strict standard notices fixed.
• Fix – Distorted pop-up display in mobile phone portrait view with new pop-up static max wide.

1.0.4 – 2013/12/20

• Feature – a3rev Plugin Framework admin interface upgraded to 100% Compatibility with WordPress v3.8.0 with backward compatibility.
• Feature – a3rev framework 100% mobile and tablet responsive, portrait and landscape viewing.
• Tweak – Upgraded dashboard switches and sliders to Vector based display that shows when WordPress version 3.8.0 is activated.
• Tweak – Upgraded all plugin .jpg icons and images to Vector based display for full compatibility with new WordPress version.
• Tweak – Yellow sidebar on Pro Version Menus does not show in Mobile screens to optimize admin panel screen space.
• Tweak – Tested 100% compatible with WP 3.8.0
• Fix – Upgraded array_textareas type for Padding, Margin settings on the a3rev plugin framework

1.0.3 – 2013/10/10

• Feature – Admin panel intuitive app interface feature. Show slider to set corner radius when select Round, hide when select Square on Border Corner Style Switch. (Pro Version Feature)
• Tweak – a3rev logo image now resizes to the size of the yellow sidebar in tablets and mobiles.
• Fixe – Intuitive Radio Switch settings not saving. Input with disabled attribute could not parse when form is submitted, replace disabled with custom attribute: checkbox-disabled
• Fix – App interface Radio switches not working properly on Android platform, replace removeProp() with removeAttr() function script

1.0.2 – 2013/10/03

• Feature – Upgraded the plugin to the newly developed a3rev admin panel app interface.
• Feature – New admin UI features check boxes replaced by switches, some dropdowns replaced by sliders.
• Feature – Replaced colour picker with new WordPress 3.6.0 colour picker (Pro Version feature).
• Feature – Added choice of 350 Google fonts to the existing 17 websafe fonts in all new single row font editor (Pro Version features).
• Feature – New Border / Button shadow features. Create shadow external or internal, set wide of shadow (Pro Version Features).
• Feature – New on page instant previews for Fonts editor, create border and shadow style.(Pro Version Features).
• Feature – Added intuitive triggers for some settings. When selected corresponding feature settings appear (Pro Version features).
• Feature – Added set pop up wide from 50% to 100% by increments of + or – 1% using new slider interface (Pro Version features)
• Tweak – Moved admin from WooCommerce settings tab onto the WooCommerce menu.
• Fix – PayPal as a security feature blocks POST request from checkout in iframe pop-up. Added feature that when /checkout URL is requested in pop-up it auto closes and redirects user to the sites checkout.
• Fix – Plugins admin script and style not loading in Firefox with SSL on admin. Stripped http// and https// protocols so browser will use the protocol that the page was loaded with.

1.0.1 – 2013/09/03

• Tweak – Tested for full compatibility with WordPress v3.6.0
• Fix – Updated some prefixes to a3rev_ for compatibility with the a3revFramework.

1.0.0 – 2013/08/05

Quick links

 
Thanks for your support !

Latest versions

Quick News

As most already expected it, the HAProxyConf 2020 which was initially planned around November will be postponed to a yet unknown date in 2021 depending on how the situation evolves regarding the pandemic. At this point it's useless to forecast anything, so we'll start to announce it upfront once we have a better visibility of what is possible. In the mean time, if you're impatient, please be aware that all the 2019 talks are available on https://www.haproxyconf.com/2019/presentations/.

July 7th, 2020 : HAProxy 2.2.0 is ready!

HAProxy 2.2 is tha latest LTS release, delivered few weeks late, but for good given that many early bugs were addressed during this time! New features include runtime certificate addition and crtlist management, dynamic error pages and return statements, logging over TCP, refined idle connection pools saving server resources, extensible health checks, improved I/O processing and scheduling for even lower latency processing, even more debugging information. Please check the announce here for more details.

November 25th, 2019 : HAProxy 2.1.0 is out!

Delivered on time, for once, proving that our new development process works better. In short this provides hot-update of certificates, FastCGI to backends, better performance, more debugging capabilities and some extra goodies. Please check the announce here for more details.

Older news...

Description

HAProxy is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for very high traffic web sites and powers quite a number of the world's most visited ones. Over the years it has become the de-facto standard opensource load balancer, is now shipped with most mainstream Linux distributions, and is often deployed by default in cloud platforms. Since it does not advertise itself, we only know it's used when the admins report it :-)

Its mode of operation makes its integration into existing architectures very easy and riskless, while still offering the possibility not to expose fragile web servers to the net, such as below :

We always support at least two active versions in parallel and an extra old one in critical fixes mode only. The currently supported versions are :

• version 2.2 : runtime certificate additions, improved idle connection management, logging over TCP, HTTP "return" directive, errorfile templates, TLSv1.2 by default, extensible health-checks
• version 2.1 : improved I/Os and multi-threading, FastCGI, runtime certificate updates, HTX-only, improved debugging, removal of obsolete keywords
• version 2.0 : gRPC, layer 7 retries, process manager, SSL peers, log load balancing/sampling, end-to-end TCP fast-open, automatic settings (maxconn, threads, HTTP reuse, pools), ...
• version 1.9 : improved multi-threading, end-to-end HTTP/2, connection pools, queue priority control, stdout logging, ...
• version 1.8 : multi-threading, HTTP/2, cache, on-the fly server addition/removal, seamless reloads, DNS SRV, hardware SSL engines, ...
• version 1.7 : added server hot reconfiguration, content processing agents, multi-type certs, ...
• version 1.6 : added DNS resolution support, HTTP connection multiplexing, full stick-table replication, stateless compression, ...
• version 1.5 : added SSL, IPv6, keep-alive, DDoS protection, ...

Main features

Each version brought its set of features on top of the previous one. Upwards compatibility is a very important aspect of HAProxy, and even version 1.5 is able to run with configurations made for version 1.0 13 years before. Version 1.6 dropped a few long-deprecated keywords and suggests alternatives. The most differenciating features of each version are listed below :

• version 1.5, released in 2014 This version further expands 1.4 with 4 years of hard work : native SSL support on both sides with SNI/NPN/ALPN and OCSP stapling, IPv6 and UNIX sockets are supported everywhere, full HTTP keep-alive for better support of NTLM and improved efficiency in static farms, HTTP/1.1 compression (deflate, gzip) to save bandwidth, PROXY protocol versions 1 and 2 on both sides, data sampling on everything in request or response, including payload, ACLs can use any matching method with any input sample maps and dynamic ACLs updatable from the CLI stick-tables support counters to track activity on any input sample custom format for logs, unique-id, header rewriting, and redirects, improved health checks (SSL, scripted TCP, check agent, ...), much more scalable configuration supports hundreds of thousands of backends and certificates without sweating
• version 1.4, released in 2010 This version has brought its share of new features over 1.3, most of which were long awaited : client-side keep-alive to reduce the time to load heavy pages for clients over the net, TCP speedups to help the TCP stack save a few packets per connection, response buffering for an even lower number of concurrent connections on the servers, RDP protocol support with server stickiness and user filtering, source-based stickiness to attach a source address to a server, a much better stats interface reporting tons of useful information, more verbose health checks reporting precise statuses and responses in stats and logs, traffic-based health to fast-fail a server above a certain error threshold, support for HTTP authentication for any request including stats, with support for password encryption, server management from the CLI to enable/disable and change a server's weight without restarting haproxy, ACL-based persistence to maintain or disable persistence based on ACLs, regardless of the server's state, log analyzer to generate fast reports from logs parsed at 1 Gbyte/s,
• version 1.3, released in 2006 This version has brought a lot of new features and improvements over 1.2, among which content switching to select a server pool based on any request criteria, ACL to write content switching rules, wider choice of load-balancing algorithms for better integration, content inspection allowing to block unexpected protocols, transparent proxy under Linux, which allows to directly connect to the server using the client's IP address, kernel TCP splicing to forward data between the two sides without copy in order to reach multi-gigabit data rates, layered design separating sockets, TCP and HTTP processing for more robust and faster processing and easier evolutions, fast and fair scheduler allowing better QoS by assigning priorities to some tasks, session rate limiting for colocated environments, etc...

Version 1.2 has been in production use since 2006 and provided an improved performance level on top of 1.1. It is not maintained anymore, as most of its users have switched to 1.3 a long time ago. Version 1.1, which has been maintaining critical sites online since 2002, is not maintained anymore either. Users should upgrade to 1.4 or 1.5.

Supported platforms

HAProxy is known to reliably run on the following OS/Platforms :

• Linux 2.4 on x86, x86_64, Alpha, Sparc, MIPS, PARISC
• Linux 2.6-5.x on x86, x86_64, ARM, AARCH64, MIPS, Sparc, PPC64
• Solaris 8/9 on UltraSPARC 2 and 3
• Solaris 10 on Opteron and UltraSPARC
• FreeBSD 4.10 - current on x86
• OpenBSD 3.1 to -current on i386, amd64, macppc, alpha, sparc64 and VAX (check the ports)
• AIX 5.1 - 5.3 on Power™ architecture

Highest performance is achieved with modern operating systems supporting scalable polling mechanisms such as epoll on Linux 2.6/3.x or kqueue on FreeBSD and OpenBSD. This requires haproxy version newer than 1.2.5. Fast data transfers are made possible on Linux 3.x using TCP splicing and haproxy 1.4 or 1.5. Forwarding rates of up to 40 Gbps have already been achieved on such platforms after a very careful tuning. While Solaris and AIX are supported, they should not be used if extreme performance is required.

Current typical 1U servers equipped with a dual-core Opteron or Xeon generally achieve between 15000 and 40000 hits/s and have no trouble saturating 2 Gbps under Linux.

Performance

[ warning: information in this section dates 2007, things have improved by an order of magnitude since then ]
Well, since a user's testimony is better than a long demonstration, please take a look at Chris Knight's experience with haproxy saturating a gigabit fiber in 2007 on a video download site. Since then, the performance has significantly increased and the hardware has become much more capable, as my experiments with Myricom's 10-Gig NICs have shown two years later. Now as of 2014, 10-Gig NICs are too limited and are hardly suited for 1U servers since they do rarely provide enough port density to reach speeds above 40-60 Gbps in a 1U server. 100-Gig NICs are coming and I expect to run new series of tests when they are available.

HAProxy involves several techniques commonly found in Operating Systems architectures to achieve the absolute maximal performance :

• a single-process, event-driven model considerably reduces the cost of context switch and the memory usage. Processing several hundreds of tasks in a millisecond is possible, and the memory usage is in the order of a few kilobytes per session while memory consumed in preforked or threaded servers is more in the order of megabytes per process.
• O(1) event checker on systems that allow it (Linux and FreeBSD) allowing instantaneous detection of any event on any connection among tens of thousands.
• Delayed updates to the event checker using a lazy event cache ensures that we never update an event unless absolutely required. This saves a lot of system calls.
• Single-buffering without any data copy between reads and writes whenever possible. This saves a lot of CPU cycles and useful memory bandwidth. Often, the bottleneck will be the I/O busses between the CPU and the network interfaces. At 10-100 Gbps, the memory bandwidth can become a bottleneck too.
• Zero-copy forwarding is possible using the system call under Linux, and results in real zero-copy starting with Linux 3.5. This allows a small sub-3 Watt device such as a Seagate Dockstar to forward HTTP traffic at one gigabit/s.
• MRU memory allocator using fixed size memory pools for immediate memory allocation favoring hot cache regions over cold cache ones. This dramatically reduces the time needed to create a new session.
• Work factoring, such as multiple at once, and the ability to limit the number of per iteration when running in multi-process mode, so that the load is evenly distributed among processes.
• CPU-affinity is supported when running in multi-process mode, or simply to adapt to the hardware and be the closest possible to the CPU core managing the NICs while not conflicting with it.
• Tree-based storage, making heavy use of the Elastic Binary tree I have been developping for several years. This is used to keep timers ordered, to keep the runqueue ordered, to manage round-robin and least-conn queues, to look up ACLs or keys in tables, with only an O(log(N)) cost.
• Optimized timer queue : timers are not moved in the tree if they are postponed, because the likeliness that they are met is close to zero since they're mostly used for timeout handling. This further optimizes the ebtree usage.
• optimized HTTP header analysis : headers are parsed an interpreted on the fly, and the parsing is optimized to avoid an re-reading of any previously read memory area. Checkpointing is used when an end of buffer is reached with an incomplete header, so that the parsing does not start again from the beginning when more data is read. Parsing an average HTTP request typically takes half a microsecond on a fast Xeon E5.
• careful reduction of the number of expensive system calls. Most of the work is done in user-space by default, such as time reading, buffer aggregation, file-descriptor enabling/disabling.
• Content analysis is optimized to carry only pointers to original data and never copy unless the data needs to be transformed. This ensures that very small structures are carried over and that contents are never replicated when not absolutely necessary.

All these micro-optimizations result in very low CPU usage even on moderate loads. And even at very high loads, when the CPU is saturated, it is quite common to note figures like 5% user and 95% system, which means that the HAProxy process consumes about 20 times less than its system counterpart. This explains why the tuning of the Operating System is very important. This is the reason why we ended up building our own appliances, in order to save that complex and critical task from the end-user.

In production, HAProxy has been installed several times as an emergency solution when very expensive, high-end hardware load balancers suddenly failed on Layer 7 processing. Some hardware load balancers still do not use proxies and process requests at the packet level and have a great difficulty at supporting requests across multiple packets and high response times because they do no buffering at all. On the other side, software load balancers use TCP buffering and are insensible to long requests and high response times. A nice side effect of HTTP buffering is that it increases the server's connection acceptance by reducing the session duration, which leaves room for new requests.

There are 3 important factors used to measure a load balancer's performance :

• The session rate
  This factor is very important, because it directly determines when the load balancer will not be able to distribute all the requests it receives. It is mostly dependant on the CPU. Sometimes, you will hear about requests/s or hits/s, and they are the same as sessions/s in or with keep-alive disabled. Requests/s with keep-alive enabled is generally much higher (since it significantly reduces system-side work) but is often meaningless for internet-facing deployments since clients often open a large amount of connections and do not send many requests per connection on avertage. This factor is measured with varying object sizes, the fastest results generally coming from empty objects (eg: or response codes). Session rates around 100,000 sessions/s can be achieved on Xeon E5 systems in 2014.
• The session concurrency
  This factor is tied to the previous one. Generally, the session rate will drop when the number of concurrent sessions increases (except with the or polling mechanisms). The slower the servers, the higher the number of concurrent sessions for a same session rate. If a load balancer receives 10000 sessions per second and the servers respond in 100 ms, then the load balancer will have 1000 concurrent sessions. This number is limited by the amount of memory and the amount of file-descriptors the system can handle. With 16 kB buffers, HAProxy will need about 34 kB per session, which results in around 30000 sessions per GB of RAM. In practise, socket buffers in the system also need some memory and 20000 sessions per GB of RAM is more reasonable. Layer 4 load balancers generally announce millions of simultaneous sessions because they need to deal with the TIME_WAIT sockets that the system handles for free in a proxy. Also they don't process any data so they don't need any buffer. Moreover, they are sometimes designed to be used in Direct Server Return mode, in which the load balancer only sees forward traffic, and which forces it to keep the sessions for a long time after their end to avoid cutting sessions before they are closed.
• The data forwarding rate
  This factor generally is at the opposite of the session rate. It is measured in Megabytes/s (MB/s), or sometimes in Gigabits/s (Gbps). Highest data rates are achieved with large objects to minimise the overhead caused by session setup and teardown. Large objects generally increase session concurrency, and high session concurrency with high data rate requires large amounts of memory to support large windows. High data rates burn a lot of CPU and bus cycles on software load balancers because the data has to be copied from the input interface to memory and then back to the output device. Hardware load balancers tend to directly switch packets from input port to output port for higher data rate, but cannot process them and sometimes fail to touch a header or a cookie. Haproxy on a typical Xeon E5 of 2014 can forward data up to about 40 Gbps. A fanless 1.6 GHz Atom CPU is slightly above 1 Gbps.

A load balancer's performance related to these factors is generally announced for the best case (eg: empty objects for session rate, large objects for data rate). This is not because of lack of honnesty from the vendors, but because it is not possible to tell exactly how it will behave in every combination. So when those 3 limits are known, the customer should be aware that it will generally perform below all of them. A good rule of thumb on software load balancers is to consider an average practical performance of half of maximal session and data rates for average sized objects.

You might be interested in checking the 10-Gigabit/s page.

Reliability - keeping high-traffic sites online since 2002

Being obsessed with reliability, I tried to do my best to ensure a total continuity of service by design. It's more difficult to design something reliable from the ground up in the short term, but in the long term it reveals easier to maintain than broken code which tries to hide its own bugs behind respawning processes and tricks like this.

In single-process programs, you have no right to fail : the smallest bug will either crash your program, make it spin like mad or freeze. There has not been any such bug found in stable versions for the last 13 years, though it happened a few times with development code running in production.

HAProxy has been installed on Linux 2.4 systems serving millions of pages every day, and which have only known one reboot in 3 years for a complete OS upgrade. Obviously, they were not directly exposed to the Internet because they did not receive any patch at all. The kernel was a heavily patched 2.4 with Robert Love's patches to support time wrap-around at 497 days (which happened twice). On such systems, the software cannot fail without being immediately noticed !

Right now, it's being used in many Fortune 500 companies around the world to reliably serve billions of pages per day or relay huge amounts of money. Some people even trust it so much that they use it as the default solution to solve simple problems (and I often tell them that they do it the dirty way). Such people sometimes still use versions 1.1 or 1.2 which sees very limited evolutions and which targets mission-critical usages. HAProxy is really suited for such environments because the indicators it returns provide a lot of valuable information about the application's health, behaviour and defects, which are used to make it even more reliable. Version 1.3 has now received far more testing than 1.1 and 1.2 combined, so users are strongly encouraged to migrate to a stable 1.3 or 1.4 for mission-critical usages.

As previously explained, most of the work is executed by the Operating System. For this reason, a large part of the reliability involves the OS itself. Latest versions of Linux 2.4 have been known for offering the highest level of stability ever. However, it requires a bunch of patches to achieve a high level of performance, and this kernel is really outdated now so running it on recent hardware will often be difficult (though some people still do). Linux 2.6 and 3.x include the features needed to achieve this level of performance, but old LTS versions only should be considered for really stable operations without upgrading more than once a year. Some people prefer to run it on Solaris (or do not have the choice). Solaris 8 and 9 are known to be really stable right now, offering a level of performance comparable to legacy Linux 2.4 (without the epoll patch). Solaris 10 might show performances closer to early Linux 2.6. FreeBSD shows good performance but pf (the firewall) eats half of it and needs to be disabled to come close to Linux. OpenBSD sometimes shows socket allocation failures due to sockets staying in state when client suddenly disappears. Also, I've noticed that hot reconfiguration does not work under OpenBSD.

The reliability can significantly decrease when the system is pushed to its limits. This is why finely tuning the is important. There is no general rule, every system and every application will be specific. However, it is important to ensure that the system will never run out of memory and that it will never swap. A correctly tuned system must be able to run for years at full load without slowing down nor crashing.

Security - Not even one intrusion in 13 years

Security is an important concern when deploying a software load balancer. It is possible to harden the OS, to limit the number of open ports and accessible services, but the load balancer itself stays exposed. For this reason, I have been very careful about programming style. Vulnerabilities are very rarely encountered on haproxy, and its architecture significantly limits their impact and often allows easy workarounds. Its remotely unpredictable even processing makes it very hard to reliably exploit any bug, and if the process ever crashes, the bug is discovered. All of them were discovered by reverse-analysis of an accidental crash BTW.

Anyway, much care is taken when writing code to manipulate headers. Impossible state combinations are checked and returned, and errors are processed from the creation to the death of a session. A few people around the world have reviewed the code and suggested cleanups for better clarity to ease auditing. By the way, I'm used to refuse patches that introduce suspect processing or in which not enough care is taken for abnormal conditions.

I generally suggest starting HAProxy as because it can then jail itself in a chroot and drop all of its privileges before starting the instances. This is not possible if it is not started as because only can execute , contrary to what some admins believe.

Logs provide a lot of information to help maintain a satisfying security level. They are commonly sent over because once chrooted, the UNIX socket is unreachable, and it must not be possible to write to a file. The following information are particularly useful :

• source IP and port of requestor make it possible to find their origin in firewall logs ;
• session set up date generally matches firewall logs, while tear down date often matches proxies dates ;
• proper request encoding ensures the requestor cannot hide non-printable characters, nor fool a terminal.
• arbitrary request and response header and cookie capture help to detect scan attacks, proxies and infected hosts.
• timers help to differentiate hand-typed requests from browsers's.

HAProxy also provides regex-based header control. Parts of the request, as well as request and response headers can be denied, allowed, removed, rewritten, or added. This is commonly used to block dangerous requests or encodings (eg: the Apache Chunk exploit), and to prevent accidental information leak from the server to the client. Other features such as checking ensure that no sensible information gets accidentely cached by an upstream proxy consecutively to a bug in the application server for example.

Download

The source code is covered by GPL v2. Source code can be downloaded right here for some old versions :

• Development version (2.2) :
• Latest LTS version (2.2) :
• Previous version (2.1) :
• Previous LTS version (2.0) :
• Previous version (1.9) :
• Previous version (1.8) :
• Older version (1.7) :
• Older version (1.6) :
• Oldest version (1.5) :
• Unmaintained version (1.4) :
• Unmaintained version (1.3) :
• Unmaintained branch (1.2) :
• Various Patches :
  • Some patches for Stunnel by HAProxy Technologies (formerly Exceliance), such X-Forwarded-For, send-proxy, unix-sockets, multi-process SSL session synchronization, transparent binding and performance improvements.
  • http://www.haproxy.com/download/free/patches/linux/epoll-2.4/ : kernel patches to enable on standard Linux 2.4 kernels and on Red Hat Enterprise Linux 3.
  • HAProxy Technologies' public patch repository for other patches (stud, stunnel, linux, keepalived, ...)
  • Browse directory for other (outdated) patches.
• Browsable directory for other files (not only patches)

Documentation

There are three types of documentation now : the Reference Manual which explains how to configure HAProxy but which is outdated, the Architecture Guide which will guide you through various typical setups, and the new Configuration Manual which replaces the Reference Manual with more a explicit configuration language explanation. The official documentation is the pure-text one provided with the sources. However, Cyril Bonté's automated conversion to HTML is much easier to use and constantly up to date, so it is the preferred one when available.

• Reference Manual for version 2.3 (development) :
• Reference Manual for version 2.2 (Stable) :
• Reference Manual for version 2.1 (Stable) :
• Reference Manual for version 2.0 (Stable (LTS)) :
• Reference Manual for version 1.9 (unmaintained) :
• Reference Manual for version 1.8 (Stable (LTS)) :
• Reference Manual for version 1.7 (Critical fixes only) :
• Reference Manual for version 1.6 (Critical fixes only) :
• Reference Manual for version 1.5 (unmaintained) :
• Reference Manual for version 1.4 (unmaintained) :
• Reference Manual for version 1.3 (unmaintained) :
• Reference Manual for version 1.2 (unmaintained) :
• Reference Manual for version 1.1 (unmaintained) :
• : Architecture Guide
• Article on Load Balancing (HTML version) : worth reading for people who don't know what type of load balancer they need

In addition to Cyril's HTML converter above, an automated format converter is being developed by Pavel Lang. At the time of writing these lines, it is able to produce a PDF from the documentation, and some heavy work is ongoing to support other output formats. Please consult the project's page for more information. Here's an example of what it is able to do on version 1.5 configuration manual.

Commercial Support and availability

If you think you don't have the time and skills to setup and maintain a free load balancer, or if you're seeking for commercial support to satisfy your customers or your boss, you have the following options :

1. contact HAProxy Technologies to hire some professional services or subscribe a support contract ;
2. install HAProxy Enterprise Edition (HAPEE), which is a long-term maintained HAProxy package accompanied by a well-polished collection of software, scripts, configuration files and documentation which significantly simplifies the setup and maintenance of a completely operational solution ; it is particularly suited to Cloud environments where deployments must be fast.
3. try an ALOHA appliance (hardware or virtual), which will even save you from having to worry about the system, hardware and from managing a Unix-like system.

Add-on features and contributions

Some happy users have contributed code which may or may not be included. Others spent a long time analysing the code, and there are some who maintain ports up to date. The most difficult internal changes have been contributed in the form of paid time by some big customers who can afford to pay a developer for several months working on an opensource project. Unfortunately some of them do not want to be listed, which is the case for the largest of them.

Some contributions were developped and not merged, most often by lack of sign of interest from the users or simply because they overlap with some pending changes in a way that could make it harder to maintain future compatibility.

• Geolocation support

Quite some time ago now, Cyril Bonté contacted me about a very interesting feature he has developped, initially for 1.4, and which now supports both 1.4 and 1.5. This feature is Geolocation, which many users have been asking for for a long time, and this one does not require to split the IP files by country codes. In fact it's extremely easy and convenient to configure.

The feature was not merged yet because it does for a specific purpose (GeoIP) what we wanted to have for a more general use (map converters, session variables, and use of variables in the redirect URLs), which will allow the same features to be implemented with more flexibility (eg: extract the IP from a header, or pass the country code and/or AS number to a backend server, etc...). Cyril was very receptive to these arguments and accepted to maintain his patchset out of tree waiting for the features to be implemented (Update: 1.5-dev20 with maps now make this possible). Cyril's code is well maintained and used in production so there is no risk in using it on 1.4, except the fact that the configuration statements will change a bit once you upgrade to 1.5.

The code and documentation are available here : https://github.com/cbonte/haproxy-patches/wiki/Geolocation

• sFlow support

Neil Mckee posted a patch to the list in early 2013, and unfortunately this patch did not receive any sign of interest nor feedback, which is sad considering the amount of work that was done. I personally am clueless about sFlow and expressed my skepticism to Neil about the benefits of sampling some HTTP traffic when you can get much more detailed informations for free with existing logs.

Neil kindly responded with the following elements :

I agree that the logging you already have in haproxy is more flexible and detailed, and I acknowledge that the benefit of exporting sFlow-HTTP records is not immediately obvious.

The value that sFlow brings is that the measurements are standard, and are designed to integrate seamlessly with sFlow feeds from switches, routers, servers and applications to provide a comprehensive end to end picture of the performance of large scale multi-tier systems. So the purpose is not so much to troubleshoot haproxy in isolation, but to analyze the performance of the whole system that haproxy is part of.

Perhaps the best illustration of this is the 1-in-N sampling feature. If you configure sampling.http to be, say, 1-in-400 then you might only see a handful of sFlow records per second from an haproxy instance, but that is enough to tell you a great deal about what is going on -- in real time. And the data will not bury you even if you have a bank of load-balancers, hundreds of web-servers, a huge memcache-cluster and a fast network interconnect all contributing their own sFlow feeds to the same analyzer.

Even after that explanation, no discussion emerged on the subject on the list, so I guess there is little interest among users for now. I suspect that sFlow is probably more deployed among network equipments than application layer equipments, which could explain this situation. The code is large (not huge though) and I am not convinced about the benefits of merging it and maintaining it if nobody shows even a little bit of interest. Thus for now I prefer to leave it out of tree. Neil has posted it on GitHub here : https://github.com/sflow/haproxy.

Please, if you do use this patch, report your feedback to the mailing list, and invest some time helping with the code review and testing.

This table enumerates all known significant contributions that led to version 1.4, as well as proposed fundings and features yet to be developped but waiting for spare time. It is not more up to date though.

Some older code contributions which possibly do not appear in the table above are still listed here.

• Application Cookies

  Aleksandar Lazic and Klaus Wagner implemented this feature which was merged in 1.2. It allows the proxy to learn cookies sent by the server to the client, and to find it back in the URL to direct the client to the right server. The learned cookies are automatically purged after some inactive time.

• Least Connections load balancing algorithm

  This patch for haproxy-1.2.14 was submitted by Oleksandr Krailo. It implements a basic least connection algorithm. I've not merged this version into 1.3 because of scalability concerns, but I'm leaving it here for people who are tempted to include it into version 1.2, and the patch is really clean.

• Soft Server-Stop

  Aleksandar Lazic sent me this patch against 1.1.28 which in fact does two things. The first interesting part allows one to write a file enumerating servers which will have to be stopped, and then sending a signal to the running proxy to tell it to re-read the file and stop using these servers. This will not be merged into mainline because it has indirect implications on security since the running process will have to access a file on the file-system, while current version can run in a chrooted, empty, read-only directory. What is really needed is a way to send commands to the running process. However, I understand that some people might need this feature, so it is provided here. The second part of the patch has been merged. It allowed both an active and a backup server to share a same cookie. This may sound obvious but it was not possible earlier.

  Usage: Aleks says that you just have to write the server names that you want to stop in the file, then the running process. I have not tested it though.

• Server Weight

  Sébastien Brize sent me this patch against 1.1.27 which adds the 'weight' option to a server to provide smoother balancing between fast and slow servers. It is available here because there may be other people looking for this feature in version 1.1.
  
  I did not include this change because it has a side effect that with high or unequal weights, some servers might receive lots of consecutive requests. A different concept to provide a smooth and fair balancing has been implemented in 1.2.12, which also supports weighted hash load balancing.

  Usage: specify "" on a server line.
  Note: configurations written with this patch applied will normally still work with future 1.2 versions.

• IPv6 support for 1.1.27

  I implemented IPv6 support on client side for 1.1.27, and merged it into haproxy-1.2. Anyway, the patch is still provided here for people who want to experiment with IPv6 on HAProxy-1.1.

• Other patches

  Please browse the directory for other useful contributions.

Other Solutions

If you don't need all of HAProxy's features and are looking for a simpler solution, you may find what you need here :

• Linux Virtual Servers (LVS)
  Very fast layer 3/4 load balancing merged in Linux 2.4 and 2.6 kernels. Should be coupled with Keepalived to monitor servers. This generally is the solution embedded by default in most IP-based load balancers.
• Nginx ("engine X")
  Nginx is an excellent piece of software. Initially it's a very fast and reliable web server, but it has grown into a full-featured proxy which can also offer load-balancing capabilities. Nginx's load balancing features are less advanced than haproxy's but it can do extra things (eg: caching, running FCGI apps), which explains why they are very commonly found together. I strongly recommend it to whoever needs a fast, reliable and flexible web server !
• Pound
  Pound is very small and reasonably good. It aims at remaining small and auditable prior to being fast. It used to support SSL and keep-alive before HAProxy. Its configuration file is small and simple. It's thread-based, but can be a simpler alternative to HAProxy for a small site when the flexibility and performance of HAProxy are not required.
• Pen
  Pen is a very simple load balancer for TCP protocols. It supports source IP-based persistence for up to 2048 clients. Supports IP-based ACLs. Uses and supports higher loads than Pound but will not scale very well to thousands of simultaneous connections. It's more versatile however, and could be considered as the missing link between HAProxy and socat.

Contacts

Feel free to contact us for any questions or comments :

Some people regularly ask if it is possible to send donations, so I have set up a Paypal account for this. Click here if you want to donate.

An IRC channel for haproxy has been opened on FreeNode (but don't seek me there, I'm not) :

External links

Here are some links to possibly useful external contents I gathered on the net. I have found most of them due to their link to haproxy's site ;-)

• Health Checks and Graceful Degradation in Distributed Systems
• haproxy-auth-request: HTTP access control using subrequests
• Utiliser HAProxy pour profiter d'HTTP/2 (FR)
• HAProxy in 2018 - A load balancer with HTTP/2 and dynamic reconfig
• GlusterFS: Configuration and Setup w/ NFS-Ganesha for an HA NFS Cluster
• Service discovery at Stripe
• High Availability with HAProxy and Keepalived in AWS
• How we fine-tuned HAProxy to achieve 2,000,000 concurrent SSL connections
• Speeding up SSL - All you need to know about haproxy
• Improving load balancing with a new consistent-hashing algorithm
• ACME validation plugin for HAProxy / Let's Encrypt
• Use HAProxy to load balance 300k concurrent tcp socket connections
• Accelerating SSL Load Balancers with Intel® Xeon® v3 Processors
• Linux networking stack from the ground up (parts 1-5) (useful to whoever wants to know what happens below haproxy)
• Loadbalance your website with haproxy and varnish
• How TubeMogul Handles over One Trillon HTTP Requests a Month
• HAProxy in the era of Microservices
• Making HAProxy 1.5 replication lag aware in MySQL
• MaxCDN: How to Use HAProxy to Handle Traffic Spikes
• Varnish, SSL and HAProxy
• True Zero Downtime HAProxy Reloads
• HAProxy Is Still An Arrow in the Quiver for Those Scaling Apps
• How To Set Up SQL Load Balancing with HAProxy (Webinar)
• HAProxy running on Ubuntu Cloud on Power8, featured by Mark Shuttleworth at IBM Impact 2014 Keynote
• Guidelines for HAProxy termination in AWS
• Marcus Rueckert's talk at osc14
• How Stack Exchange gets the most out of HAProxy
• Open Source Windows service for reporting server load back to HAProxy (load balancer feedback agent).
• Load Balancing Amazon RDS Read Replica's using HAProxy
• Installing HAProxy on pfSense
• MySQL Load Balancing with HAProxy - Tutorial
• HAProxy vs Nginx benchmark for the Eucalyptus Cloud computing Platform
• WebSocket Over SSL: HAProxy, Node.js, Nginx
• Comparison Analysis:Amazon ELB vs HAProxy EC2
• Simple SPDY and NPN Negotiation with HAProxy
• Using HAProxy to Build a More Featureful Elastic Load Balancer
• 3 ways to configure haproxy for websockets
• Segregating services at bitbucket
• Load balancing FTP, by Ben Timby
• Howto setup a haproxy as fault tolerant / high available load balancer for multiple caching web proxies on RHEL/Centos/SL
• Load balancing @Tuenti, by Ricardo Bartolomé
• Benchmarking SSL performance
• Smart Content Switching for News Website
• HA Proxy for Exchange 2010 Deployment & SMTP Restriction
• A more stable MySQL with HAProxy
• Benchmarking HAProxy under VMware : Ubuntu vs FreeBSD
• Stack Overflow: Better rate limiting for all with HAProxy
• Benchmarking Load Balancers in the Cloud
• Using HAProxy for MySQL failover and redundancy
• Setting up a high availability load blancer with haproxy and keepalived on debian lenny
• Configure HAProxy with TPROXY kernel for full transparent proxy
• HAProxy, X-Forwarded-For, GeoIP, KeepAlive
• Load Balancing in Amazon EC2 with HAProxy
• CouchDB Load Balancing and Replication using HAProxy
• Zero-Downtime restarts with HAProxy
• Free your port 80 with HAProxy
• Another comparison of HAProxy and Nginx
• Scaling on EC2
• HAProxy on Opensolaris 2008.05
• Load-Balancing and QoS with HAProxy
• Reviewing Application Health with HAProxy Stats