Hi!
>> frontend rest-in
>>
>> bind *:8089 ssl crt /etc/ssl/*****
>>
>> acl host_rest_services hdr(Host) -i test-rest.net
>> <https://urldefense.proofpoint.com/v2/url?u=http-3A__test-2Drest.net&d=DwQFAg&c=_hRq4mqlUmqpqlyQ5hkoDXIVh6I6pxfkkNxQuL0p-Z0&r=BZ2S09kcMRiJIUh57WZsng&m=552Ig6nEOMH9wg2ks1WhxrWEHEMdG8cMbcbCkjD_Gog&s=UVyuxV46M6Snh0R8nhltBxZLBuVcrVsIcTLAaVp7nQg&e=>
> It would appear that your acl was not matched. It was up to `rest-in` to
> determine how to route the request, and since there's no other backend to
> choose from, there was no place for the request to go. I would advise that
> you validate your acl is configured as you desired.
>
My guess would be that the Host header actually says “test-rest.net:8089
<http://test-rest.net:8089/>”, which would lead the ACL to not match.
> It would also be a good idea to setup a `default backend` as a way to help
> test where your requests are going.
>
For debugging these kinds of things I usually run haproxy in debug mode:
haproxy -d -f haproxy.cfg
That way it will echo incoming and outgoing headers.
Daniel
--
Daniel Schneller
Principal Cloud Engineer
CenterDevice GmbH | Hochstraße 11
| 42697 Solingen
tel: +49 1754155711 | Deutschland
daniel.schnel...@centerdevice.de | www.centerdevice.de
Geschäftsführung: Dr. Patrick Peschlow, Dr. Lukas Pustina,
Michael Rosbach, Handelsregister-Nr.: HRB 18655,
HR-Gericht: Bonn, USt-IdNr.: DE-815299431
