In 1.0.0-rc.2, the behavior of the limit parameter was changed, nominally to align with the behavior defined in OGC API Part 1. However, we have since realized that (1) the behavior described there is not internally-consistent and (2) has since been changed the draft/corrigendum of that spec.
The new behavior is defined that if a client requests a limit value above the maximum advertised by the server, that the server should treat the request as if the limit parameter were the maximum value. It must not respond with a error because the the limit value, and must respond with no more than that many items.
In 1.0.0-rc.2, the behavior of the limit parameter was changed, nominally to align with the behavior defined in OGC API Part 1. However, we have since realized that (1) the behavior described there is not internally-consistent and (2) has since been changed the draft/corrigendum of that spec.
See:
The new behavior is defined that if a client requests a limit value above the maximum advertised by the server, that the server should treat the request as if the limit parameter were the maximum value. It must not respond with a error because the the limit value, and must respond with no more than that many items.