Affects Version/s: 2.0
Fix Version/s: None
Component/s: Content Targeting
Audience targeting analytics processor url is not composed correctly when Liferay is installed in non-root context.
This makes Audience targeting not to to work correctly but the biggest problem is that in combination with WebSphere the WebSeal component rewrites the false request uri to the right one and Audience Targeting pushes back a new jsessionid which resets the whole session and makes the portal non usable.
Steps to reproduce:
1) Install Liferay in context "/liferay"
2) Install Audience targeting plugin
3) Check from browser's developer tools the "track" component request uri
Expected result: The uri should be http://localhost:9080/liferay/o/analytics-processor/track
Actual result: The uri should be http://localhost:9080/o/analytics-processor/track