RFC 4236:HTTP Adaptation with Open Pluggable Edge ...
RFC-Ref

HTTP profile


Click on the red underlined text to get to the source

... application-agnostic OPES documents and this HTTP profile constitute a complete specification for HTTP adaptation with OPES ...


... This section documents the HTTP profile for the OPES Callout Protocol (OCP ...
... RFC4037]. Familiarity with OCP Core is required to understand the HTTP profile. This section uses OCP Core conventions, terminology, and mechanisms. ...
... HTTP message parts are documented in Section 3.1. HTTP profile introduces a new parameter for the Application Message Start (AMS) message to communicate known HTTP message ...
... This document defines two HTTP profiles for OCP: request and response ...
... Encodings (Section 3.2.7) The definition of the HTTP profile feature structure using PETDM follows: ...
... Figure 2 An HTTP profile structure can be used in feature lists of Negotiation Offer (NO) messages and as an anonymous parameter of a Negotiation Response ...
... that is a part of an OCP transaction with an HTTP profile. The AM- Part parameter value ...
... The HTTP profile for OCP applies to all HTTP messages. That scope ...


... application-agnostic OPES specifications. HTTP profiles do not introduce any HTTP-specific security considerations ...


... OPES mechanisms is defined in corresponding application-agnostic specifications. HTTP profiles for these mechanisms use corresponding compliance definitions from these specifications, as if each profile ...



Google
Web
RFC-Ref