Re: CSS11500 rule matching breaks
Dane Ruyle <[email protected]>
| Newsgroups | gmane.comp.programming.load-balancing.general |
|---|---|
| Message-ID | <[email protected]> |
> Moreover, the problem is very much lessened, although not completely solved, when we add the configuration command "flow permanent port1 80" to our setup. Unfortunately I don't know what's going on inside the box to determine precisely *why* this command is having such an effect. Umm, I'm an old, rusty CSS guy from wayyyy back. So, forgive me if this sounds lame and unrelated. :) Are you specifying the port # in the service and content rules? It used to be, I believe, if you did not specify a port, it would listen for any port and try to find a match. It is then possible, if you are using the same servers for other services, that it might get misdirected somehwere, somehow...? Just throwing that out there. Other than that, how are the CSSes working out for you? Thanks and good luck, Dane _________________________________________________________________ See how Windows Mobile brings your life together—at home, work, or on the go. http://clk.atdmt.com/MRT/go/msnnkwxp1020093182mrt/direct/01/ _______________________________________________ lb-l mailing list [email protected] http://vegan.net/mailman/listinfo/lb-l Searchable Archive: http://vegan.net/lb/archive http://lbdigest.com Load Balancing Digest http://lbwiki.com Load Balancing Wiki