Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 329875

Summary:	Support for overlapping HTTP applications
Product:	z_Archived	Reporter:	Gunnar Wagenknecht <gunnar>
Component:	gyrex	Assignee:	Gunnar Wagenknecht <gunnar>
Status:	RESOLVED FIXED	QA Contact:
Severity:	normal
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Gunnar Wagenknecht

2010-11-10 04:49:32 EST

Gyrex allows arbitrary URLs to applications. We need to investigate and define clear rules for overlapping applications.

Example:
  app1 - http://localhost/myapp
  app2 - http://localhost/myapp/admin


- Will they share sessions? 

The current thinking is not. They are different applications. However, we need to investigate session handling with overlapping applications. It may be necessary to use a application individual session cookies. 


- Should we support this at all?

The above case is quite common. There is a regular app and an admin app. Implementing the admin area as a separate app has some advantages (eg. different sessions). 


- Which app wins over the URL?

Should be the longest matching path, i.e. in the example above, app1 will have no luck with any servlet/resource registered under "/admin". We just need to ensure that the implementation does it this way and properly document it.

Comment 1 Gunnar Wagenknecht

2012-05-14 03:29:38 EDT

This works as documented. Jetty (i.e. the container) takes care of the Cookie vs. Session ID stuff.