Re: Receiving HTTP responses to TCP pool

Its a feature, a frontend running with tcp can use a backend using http. If you want both to use tcp either put that in the defaults, or specify it for both frontend&backend. It seems to me your assumption that the backend automaticaly takes over the mode from the frontend is wrong. Perhaps a

Re: Receiving HTTP responses to TCP pool

I think that nails the problem. So if its not just me then the question is if this is intended behavior or if its a bug. If its intended then I don't think its entirely clear from the documentation that 'mode tcp' only works under certain circumstances. If we confirm that its a bug then I'd be will

Re: Receiving HTTP responses to TCP pool

Which does not prevent the backend from using mode http as the defaults section sets. CJ Ess schreef op 16-6-2015 om 22:36: "mode tcp" is already present in mainfrontend definition below the bind statement On Mon, Jun 15, 2015 at 3:05 PM, PiBa-NL > wrote:

Re: Receiving HTTP responses to TCP pool

"mode tcp" is already present in mainfrontend definition below the bind statement On Mon, Jun 15, 2015 at 3:05 PM, PiBa-NL wrote: > CJ Ess schreef op 15-6-2015 om 20:52: > > This one has me stumped - I'm trying to proxy SMTP connections however I'm > getting an HTTP response when I try to conn

Re: Receiving HTTP responses to TCP pool

CJ Ess schreef op 15-6-2015 om 20:52: This one has me stumped - I'm trying to proxy SMTP connections however I'm getting an HTTP response when I try to connect to port 25 (even though I've done mode tcp). This is the smallest subset that reproduced the problem - I can make this work by doing