pfsense-packages/.git - pfSense packages repository

	Commit message (Collapse)	Author	Age	Files	Lines
*	haproxy-devel, small fixes	PiBa-NL	2015-12-12	3	-18/+40
\|
*	haproxy-devel, append duplicate name to with -copy	PiBa-NL	2015-11-05	2	-2/+4
\|
*	haproxy-devel, user gui permissions, show backend usage, use-server action	PiBa-NL	2015-11-01	2	-34/+30
\|
*	haproxy-devel,	PiBa-NL	2015-10-27	3	-11/+354
\| \| \| \| \| \|	-acls/actions in backend -prevent filling backend selections items that have value none when renaming a backend -example template for using multiple domains on 1 frontend
*	haproxy-devel, avoid possible config upgrade error messages, add actually ↵	PiBa-NL	2015-10-24	2	-8/+27
\| \| \| \|	writhing the configured frontend errorfiles to the config
*	haproxy-devel, pkg v0.32 allow usage of mailers/dns/'actions', rework of acl ↵	PiBa-NL	2015-10-24	8	-306/+596
\| \| \| \|	system.
*	haproxy-devel, fix package for pfsense 2.1.5, bump pkg v0.28	PiBa-NL	2015-08-20	3	-10/+140
\| \| \| \| \| \| \|	-add email settings for 1.6-dev version -remove call to nonexisting javascript function -put a maximum height to a table textarea + scrollbar -remove httpchk from config file when not used
*	haproxy-devel, dont send the root CA cert to clients when using ↵	PiBa-NL	2015-06-20	2	-2/+3
\| \| \| \| \| \| \|	ssl-offloading, its not needed. -cipher example and HSTS textual addition -another try to include lua for haproxy1.6dev package binary
*	haproxy-devel, new functionality SSL OCSP stapling for haproxy	PiBa-NL	2015-05-24	1	-1/+7
\| \| \| \|	-fix server dns resolving in case a CNAME is used.
*	haproxy-devel, move files to subfolders	PiBa-NL	2015-02-21	10	-0/+3839
\|
*	haproxy-devel, several improvements / fixes:	PiBa-NL	2015-02-02	1	-0/+43
	-combine certificate acl's with user acl's -wildcard certificate acl handling -better handeling of 'transparent' backends when using mixed ipv4 and ipv6, a single defined backend can write 2 backends to the config ipv4 / ipv6 -option to negate a acl -moved acl definitions above advanced user config in cfg (to allow user config to use already defined acls) -toggle in frontend overview to easily enable/disable a frontend