Hi Shawn On 26/04/2024 18:34, Shawn Heisey wrote: > I was just reading about the new "option forwarded" capability in 2.9, > so I added it to my config and now I get warnings when checking the config. > > [WARNING] (253408) : config : parsing [/etc/haproxy/haproxy.cfg:45] : > 'option forwarded' ignored because frontend 'web80' has no backend > capability. > [WARNING] (253408) : config : parsing [/etc/haproxy/haproxy.cfg:60] : > 'option forwarded' ignored because frontend 'web' has no backend > capability. > > This is the line I added to the frontends: > > option forwarded except 127.0.0.1 > > I realized I don't need it on 'web80', so I removed that one. > > The 'web' frontend does use backends. Its default backend has no > servers and denies all requests -- the request must match one of the > ACLs to choose a backend that actually does something. > > I suspect that I can ignore this warning, but I want to check here and > make sure. Can I set something so it doesn't emit the warning? > > Thanks, > Shawn > >
This is expected because forwarded cannot be used on frontends unlike the good old forwardfor: This is expected because forwarded cannot be used on frontend unlike forwardfor: > -- keyword -------------------------- defaults - frontend - listen -- backend > - > option forwardfor X X X X > option forwarded (*) X - X X (excerpt from the documentation) This was done on purpose because in practice the option is only relevant at the backend side, and supporting forwardfor in both frontend and backend config sections has caused multiple issues in the past because of the added complexity (requires extra care to check for the option on the proper section, depending if it's set in the frontend or the backend or both...), and we wanted to get rid of that extra complexity from the start when implementing the new forwarded option. Thus for the option to be considered, you should add it to your default or backend sections :) Does that help? Regards, Aurelien
