Pivotal Knowledge Base

Follow

How does PWS route requests to your application?

Environment

Pivotal Web Services (PWS): All versions

Purpose

This article describes how PWS route incoming requests to your applications hosted on PWS.

Procedure

The load-balancing algorithm is Round-robin at this point, so that requests from the same client in the same session may be routed to different app instances. 

PWS supports session affinity or sticky sessions for incoming HTTP requests to applications if a JSESSIONID cookie is used. If multiple instances of an application are running on PWS, all requests from a given client will be routed to the same application instance. This allows application containers and frameworks to store session data specific to each user session.

Risks

Regarding sticky session, if you're using a language/framework that uses a session cookie with a different name like PHPSESSID, you need to configure it to use JSESSIONID or sticky sessions will not work.

Comments

Powered by Zendesk