Project

General

Profile

Actions

Bug #12692

closed

Haproxy backend issue

Added by Viktor Gurov 4 months ago. Updated 4 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
haproxy
Target version:
-
Start date:
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:

Description

https://forum.netgate.com/topic/168944/haproxy-backend-issue:
It seems that when not setting HSTS value to something, haproxy will not allow to save backend.

Results in:
The following input errors were detected:
The field 'Strict-Transport-Security' is not empty or a number.

But it`s incorrect as value IS empty.
Using haproxy-devel net 0.62_6


Related issues

Related to Bug #10937: HAProxy frontend and backend entry limitResolvedViktor Gurov09/29/2020

Actions
Actions #1

Updated by Viktor Gurov 4 months ago

  • Related to Bug #10937: HAProxy frontend and backend entry limit added
Actions #3

Updated by Jim Pingle 4 months ago

  • Status changed from New to Pull Request Review
  • Assignee set to Viktor Gurov
Actions #4

Updated by Viktor Gurov 4 months ago

  • Status changed from Pull Request Review to Feedback
Actions #5

Updated by Danilo Zrenjanin 4 months ago

Tested against:

2.6.0-RC (amd64)
built on Mon Jan 17 23:21:01 UTC 2022
FreeBSD 12.3-STABLE

HA proxy devel 0.62_7.

I am getting more than just one error after trying to save a backend:

The following input errors were detected:

    The field 'Check frequency' value is not a number.
    The field 'Connection timeout' value is not a number.
    The field 'Server timeout' value is not a number.
    The field 'Retries' value is not a number.
    The field 'Strict-Transport-Security' is not empty or a number.

All those fields should be using default values if nothing was defined. Please check.

Actions #6

Updated by Viktor Gurov 4 months ago

Danilo Zrenjanin wrote in #note-5:

All those fields should be using default values if nothing was defined. Please check.

No such issue on pfSense 2.7.0.a.20220120.0600 with pfSense-pkg-haproxy-devel 0.62_8
Please check again

Actions #7

Updated by → luckman212 4 months ago

So just checking... the fix is only in pfSense 2.7 alpha? Not making it into 2.6 / 22.01 ?

Is there way to pull it in early via System Patches?

edit: I needed this now so I ended up just manually grabbing the raw php files and clobbering the existing ones

fetch https://raw.githubusercontent.com/pfsense/FreeBSD-ports/devel/net/pfSense-pkg-haproxy-devel/files/usr/local/www/haproxy/haproxy_listeners_edit.php
fetch https://raw.githubusercontent.com/pfsense/FreeBSD-ports/devel/net/pfSense-pkg-haproxy-devel/files/usr/local/www/haproxy/haproxy_pool_edit.php
mv -f haproxy* /usr/local/www/haproxy/
Actions #8

Updated by Viktor Gurov 4 months ago

Merged to 22.01/2.6

Actions #9

Updated by Marcos Mendoza 4 months ago

  • Status changed from Feedback to Resolved

After upgrading, I was able to correctly save the backend. Before, I was not able to save without the multiple input validation errors coming up.

Actions #10

Updated by Danilo Zrenjanin 4 months ago

→ luckman212 wrote in #note-7:

So just checking... the fix is only in pfSense 2.7 alpha? Not making it into 2.6 / 22.01 ?

Is there way to pull it in early via System Patches?

edit: I needed this now so I ended up just manually grabbing the raw php files and clobbering the existing ones

[...]

I tested against:

2.6.0-RC (amd64)
built on Mon Jan 24 18:44:12 UTC 2022
FreeBSD 12.3-STABLE

Everything works as expected.

Actions

Also available in: Atom PDF