Re: Alteon cookie insert and http/1.1

a big difference between HTTP 1.1 and 1.0 is that responses can be chunked.

http://developers.sun.com/mobility/midp/questions/chunking/

Another difference is pipelined requests

http://en.wikipedia.org/wiki/HTTP_pipelining

Either of these mechanisms might be contributing to the issue but my bet 
would be on the chunked responses confusing your load balancer. Maybe 
there is a setting for dealing with chunked responses on Alteon?


On 4/1/10 7:48 AM , [email protected] wrote:
> Hello,
>
> I've got a problem with an Alteon (25.0.0) which is configured to do cookie-based persistence with cookie insert mode.
> HTTP requests goes through a proxy before reaching the Alteon.
> If the proxy uses HTTP/1.1 to forward requests to the Alteon, randomly, the Alteon doesn't insert cookie in the responses. When we use HTTP/1.0 on the proxy there is no problem ; the cookie is always present in traffic going back to the proxy.
>
> The Alteon is configured like this :
>
> /c/slb/virt 5/service http
> 	group 1
> 	rport 8080
> 	dbind ena
> /c/slb/virt 5/service 80/pbind cookie insert MyCookie dname "path=/"
> /c/slb/virt 5/service 80/http/rcount 1
>
> Is there any way to use HTTP/1.1 without loosing the cookie ?
>
> Thanks in advance,
> Nicolas
> _______________________________________________
> 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
>    

_______________________________________________
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