Hi, On Mon, Mar 02, 2009 at 08:19:22PM +0800, FinalBSD wrote: > Hi there, > I'm not sure it's a bug in the snapshot(ss-20090207 and ss-20090223), but > I really cannot get the right reponse > when I use the "monitor-net" option like following: > ---------------------------------------------------- > monitor-net 192.168.1.0/24 > ---------------------------------------------------- > > after that, when I visit the vip from 192.168.1.x, I just get this response: > > 400 Bad request Your browser sent an invalid request. > > > > But the response is right when I use the release version 1.3.15.7. > Can somebody check this? I noticed that the code is different between > these two versions
Good catch, it was indeed a bug since the layered rewrite. I have fixed it and pushed it into git, it will appear in tomorrow's snapshot. If you're playing with the new version, I have also fixed a bug causing CLOSE_WAIT sessions to appear when using "tcp-request content" rules ; a close condition was missing. We're several ones using the latest snapshots in various environments ranging from home usage to production, and I think we're getting close to a release. It will certainly lack some features compared to what I wanted to put in 1.3.16 but it will help us work on a sane basis for next versions. Thanks, Willy
