This is a possible OCP message flow using an HTTP request profile.
Client wants to access the home page of www.restricted-content.org but access is denied by an URL blocking service running on the OCP server.
Notes:
- This example should be compliant to OCP Core Draft Version 04 and HTTP adaptation Draft Version 02.
| OPES processor | Callout server |
|---|---|
CS; |
CS; |
SGC 11 ({"23:ocp-test.com/url-filter"});
|
|
NO ({"37:http://iana.org/opes/ocp/HTTP/request"})
SG: 11
;
|
NR {"37:http://iana.org/opes/ocp/HTTP/request"}
SG: 11
;
|
TS 55 11; |
|
AMS 55 AM-EL: 0 ; |
|
DUM 55 0 Kept: 0 AM-Part: request-header 245:GET http://www.restricted-content.org/ HTTP/1.1 Accept: */* Accept-Language: de Accept-Encoding: gzip, deflate User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) Host: www.restricted-content.org Proxy-Connection: Keep-Alive ; |
|
AME 55; |
AMS 55; |
DUM 55 0 AM-Part: response-header 76:HTTP/1.1 403 Forbidden Content-Type: text/html Proxy-Connection: close ; |
|
DUM 55 0 AM-Part: response-body 67:<html><body>You are not allowed to access this page.</body></html> ; |
|
AME 55; |
|
TE 55; |
TE 55; |
Back to Martin's OPES page