The Profiler locates portal resources given a set of request parameters, properties, and attributes
The Profiler is invoked during the request processing pipeline.
It requires that the request context is already populated with the portal request and response,
and capability and user information. The request context parameters, properties and attributes
make up the profile criterion which the profiler uses to locate portal resources:
path
|
- Looks at the Request Path of the request.
|
group
|
- Looks in HTTP Request Parameter (Standard) for the named parameter.
- Next looks at current authenticated subject, finding all group principals for the subject.
|
role
|
- Looks in HTTP Request Parameter (Standard) for the named parameter.
- Next looks at current authenticated subject, finding all role principals for the subject.
|
user
|
- Looks in HTTP Request Parameter (Standard) for the named parameter.
- Next looks at current authenticated subject, finding all user principals for the subject.
|
language
|
- Looks in HTTP Request Parameter (Standard) for the named parameter.
- Next looks at the Locale.LanguageCode for the current request.
|
mediatype
|
- Looks in HTTP Request Parameter (Standard) for the named parameter.
- Next looks at the Mediatype (Mime Type) for the current request.
|
country
|
- Looks in HTTP Request Parameter (Standard) for the named parameter.
- Next looks at the Locale.CountryCode for the current request.
|
hard.coded
|
- Applies the value specified in this rule as a constant.
|
path.session
|
- Looks in HTTP Request Parameter (Standard) for the named parameter.
- Looks in Portal's Servlet Session for the named attribute.
|
group.user.role
|
|