Alias "/" must be called only if the request cannot be handled
--------------------------------------------------------------
Key: PAXWEB-59
URL: http://issues.ops4j.org/jira/browse/PAXWEB-59
Project: Pax Web
Issue Type: Bug
Affects Versions: 0.2.2
Reporter: Alin Dreghiciu
Assignee: Alin Dreghiciu
Fix For: 0.2.3
After the separation of servlet contexts per http contexts (in 0.2.2) the
following situation could appear:
- in context 1 two aliases were registered "/foo" and "/"
- in context 2 one alias was registered "/bar"
The registrations were done in this order.
Now, if you have a request for "bar/any" that should be handled in the context
2 by registration for "/bar", pax web was using the "/" registration from the
first context.
Another wrong selected registration was possible if you had the following:
- in context 1 two aliases were registered "/foo"
- in context 2 one alias was registered "/foo/bar"
In case of a request for "/foo/bar" or "/foo/bar/any" that should be handled by
registration from context 2, pax web was selecting the first registration (for
"/foo".
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
