Cross-Site Requests
Allows managing the allowed entries for cross-site requests.
In this section, an administrator can release access to the portal based on the characteristics of the requests.
Each request that arrives at the portal is tested against each of the rules defined here. If a rule matches the characteristics of the request, that request will be processed normally. Otherwise, an HTTP 404 error will be returned to the client.
The entries added to this service consist of:
- Request Method Pattern
- It is a regular expression that will be used to validate the request method.
- Request Path Pattern
-
It is a regular expression
that will be used to validate the path of the request. The validated path is the part of the path following the context in which the portal is
executed on the application server.
Examples:
- If the request was to
http://meuserver.com/portal/list/news.html
and the portal is being executed athttp://meuserver.com/
, the path to be validated is/portal/list/news.html
. - If the request was to
http://meuserver.com/portal/list/news.html
and the portal is being executed athttp://meuserver.com/portal/
, the path to be validated is/list/news.html
.
- If the request was to
- Request Origin Pattern
-
It is a regular expression
that will be used to validate the origin of the request. The origin of the request will be:
- If present in the request, it will be the value of the HTTP Origin header.
- If present in the request, it will be the value of the HTTP Referer header.
- An empty string, otherwise.
In addition to the entries explicitly defined here, any request whose origin matches the domain and port of any URL registered on an existing website will be accepted by the portal.
Permissions
- Manage service instance: Allows managing all data of this service instance, including deleting it entirely.
- Edit service instance content: Allows managing all data of this service instance with publisher profile.
- View service instance: Allows viewing public data of this service instance.