Re: relayd(8): transparent forward

2019-11-06 Thread mp1009
On 2019-11-06 08:25, Stuart Henderson wrote: On 2019/11/05 20:46, Mischa Peters wrote: When you are using transparent (Direct Server Return) you have to make sure you disable ARP on the servers you are load balancing. Transparent is not "direct server return", that is done with "route

Re: relayd(8): transparent forward

2019-11-05 Thread mp1009
Mischa, as you were guessing right, my sole intention was to have the actual client IP address available on the server side without changing anything in the current server configuration. With your explanation, I understand that in my case this is not possible. So, as you suggested, passing the

relayd(8): transparent forward

2019-11-05 Thread mp1009
The configuration below works fine as soon as I remove the 'transparent' keyword but times out when running as transparent forwarder. What am I missing? Any help is being appreciated. - # relayd.conf http protocol "httpsfilter" {

HTTP Cache-Control headers via httpd.conf(5)

2019-10-26 Thread mp1009
Running httpd(8) since quite a while, I'm missing an easy way to configure type dependent HTTP cache-control headers. As I consider running relayd(8) solely for that purpose kind of overkill (and I know I'm not the only one out there who thinks that way), here is a little proposal for