> > > Using such a configuration:
> > > #-8<-------
> > > table <primary> { 192.0.2.4 }
> > > table <fallback> { 192.0.2.7}
> > > http protocol www {
> > > block
> > > match request header "Host" value "www.example" tag "example"
> > > pass request tagged "example" forward to <primary>
^^^^^^^^^^^^^^^^^^^^
Wouldn't it be wrong if relayd sends the requests to <fallback> even though
you told him quite clearly to send them to <primary>?
If <primary> is down then relayd must error out, or not (because this is
what you told him to do: sending to <primary>)
I think you need an additional step between which decides where to send the
request.
Then in next step you can tag and modify...
Maybe I'm wrong but to me it sounds more consistent when doing the
layer 3 redirection on 192.0.2.30 :
table <www> { 192.0.2.4 }
table <fallback> { 192.0.2.7 }
redirect www {
listen on 192.0.2.30 port 80
forward to <www> check http "/" code 200
forward to <fallback> check icmp
}
And then do all the layer 7 filtering on 192.0.2.4
But as I said before: maybe I'm wrong ;-)
