Hello,

I'm using pound (2.0-1.2 - debian packaging) with two hosts (lighttpd) as 
backends. Session tracking works most of the times but sometimes within a 
session pound switches from one backend to the other. I'm using jmeter as an 
automated test tool and thus it's unlikely that there was an error with doing 
a wrong request or so.

When looking at the traffic, I can see that the cookie (name and content) has 
stayed the same in all the requests during that session.

Request 1-8 land on backend1, request 9 and 10 land on backend2. This is not 
reproducible though. Some sessions work just fine and stay on the same host 
(request 1-10).

Any idea why / how this happens?

I also searched for a CHANGELOG but couldn't find any. I wanted to look up 
which changes happend between the version we are using and the current stable 
one.


thanks for the good work,



Tom

I will be out of the office from March 23rd - April 1st.

I will be checking my email when possible, but will be unavailable via phone. 

If you need any immediate assistance or help please call 707 667 9479 x31 or
email support(at)streamguys.com

You can reach sales at sales(at)streamguys.com

Thank You, 

Kiriki Delany
President/CTO
www.streamguys.com
kiriki(at)streamguys.com
1.707.667.9479 x251
1.707.516.0009 fax

Hello,

On Monday, 24. March 2008, Tom Fernandes wrote:[...]

I checked in the debian documentation directory and couldn't find a CHANGELOG 
file. I now also checked the upstream source and saw that the CHANGELOG is 
actually included in e.g. Pound-2.4.tgz.

So this is a packaging bug. I will file a bugreport against the debian package 
to include the CHANGELOG file in the future.


regards,


Tom

I will be out of the office from March 23rd - April 1st.

I will be checking my email when possible, but will be unavailable via phone. 

If you need any immediate assistance or help please call 707 667 9479 x31 or
email support(at)streamguys.com

You can reach sales at sales(at)streamguys.com

Thank You, 

Kiriki Delany
President/CTO
www.streamguys.com
kiriki(at)streamguys.com
1.707.667.9479 x251
1.707.516.0009 fax

Hello again,

I found out, that this is not actually a bug but a normal behavior I guess.
Our situation is, that 1-8 are plain HTTP. Request 9-10 are HTTPS requests. So 
requests 1-8 are ListenHTTP and 9-10 are ListenHTTPS.

When switching from HTTP to HTTPS sometimes the backend changes as well.

Is there a way to keep a session on one backend even if you switch from HTTP 
to HTTPS?


thanks,


Tom


On Monday, 24. March 2008, Tom Fernandes wrote:[...]

Hello,

I found a Thread in the archive addressing exactly this topic - 
subject: "maintaining session when switching to https"

Is this still true or has there been some work on that part of the code, a 
patch available, a workaround or so?


regards,


Tom


On Monday, 24. March 2008, Tom Fernandes wrote:[...]

On Mon, 2008-03-24 at 17:38 +0100, Tom Fernandes wrote:[...]

A work-around might be possible, depending on your circumstances: if you
can live with global services (i.e. a Service defined outside of the
Listen blocks, either because everything goes to the same back-ends, or
because you can discriminate by headers), then the session will be
maintained there, regardless of how the request came in. For example:

ListenHTTP
    Address     1.2.3.4
    Port        80
End

ListenHTTPS
    Address     1.2.3.4
    Port        443
    Cert        "server.pem"
    AddHeader   "X-SSL: on"
End

Service "common"
    HeadRequire "^Host:.*yourhost.*"
    BackEnd
        Address     192.168.101.1
        Port        80
    End
    BackEnd
        Address     192.168.101.2
        Port        80
    End
    Session
        Type COOKIE
	ID "mySessionTracker"
        TTL 300
    End
End

Hope this helps.[...]