For classic RODL-based servers the HttpAPI based attributes have to be set via RODL.
The following custom attributes can be applied to RODL methods:
HttpApiPath
HttpApiMethod
HttpApiResult
HttpApiTags
HttpApiOperationId
These custom RODL attributes have exactly the same meaning as the corresponding attribute properties in a CodeFirst server.
However due to the text-only nature of custom RODL attribute values the HttpApiResult and HttpApiTags attributes are set in a slightly different way:
HttpApiResult value should be a numeric Http response code. F.e. the value of this attribute can be set to “200” or “201” but it cannot be set to “OK” or “Created” .
HttpApiTags should be set to a comma-separated list of tags, f.e. "sometag,someothertag"
Also service method parameter can be marked with RODL attributes HttpApiQueryParameter or HttpApiHeaderParameter . If the value of this attribute is set to 1 then it is expected that the marked parameter will be passed via Url query string or Http headers accordingly