In the process of moving to a more flexible GET/POST independent query protocol currently there is:
a must on allowing HTTP GET
a should on allowing HTTP POST
to preserve compatibility with legacy services using extra query arguments that prevent appending /capabilities or other endpoints to the registered base_url.
Should we keep going this way, maybe alerting that GET-only will be deprecated in the future?
Should we allow REQUEST to handle getCapabilities and such where extra query args are present? (this poses an issue on registering the dual behaviour of services)
In the process of moving to a more flexible GET/POST independent query protocol currently there is:
Should we keep going this way, maybe alerting that GET-only will be deprecated in the future? Should we allow
REQUEST
to handle getCapabilities and such where extra query args are present? (this poses an issue on registering the dual behaviour of services)