#### [Abblix\.Oidc\.Server](https://www.abblix.com/en/docs/api/abblix-oidc-server 'index')
### [Abblix\.Oidc\.Server\.Common\.Configuration](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Common.Configuration 'Abblix\.Oidc\.Server\.Common\.Configuration')

## RegistrationRequestSizeValidator Class

Refuses at startup a [MaxRegistrationRequestSize](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Common.Configuration.OidcOptions#Abblix.Oidc.Server.Common.Configuration.OidcOptions.MaxRegistrationRequestSize 'Abblix\.Oidc\.Server\.Common\.Configuration\.OidcOptions\.MaxRegistrationRequestSize') that no request could satisfy\.

```csharp
public sealed class RegistrationRequestSizeValidator : Microsoft.Extensions.Options.IValidateOptions<Abblix.Oidc.Server.Common.Configuration.OidcOptions>
```

Inheritance [System\.Object](https://learn.microsoft.com/en-us/dotnet/api/system.object 'System\.Object') → RegistrationRequestSizeValidator

Implements [Microsoft\.Extensions\.Options\.IValidateOptions&lt;](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.options.ivalidateoptions-1 'Microsoft\.Extensions\.Options\.IValidateOptions\`1')[OidcOptions](https://www.abblix.com/en/docs/api/abblix-oidc-server/Abblix.Oidc.Server.Common.Configuration.OidcOptions 'Abblix\.Oidc\.Server\.Common\.Configuration\.OidcOptions')[&gt;](https://learn.microsoft.com/en-us/dotnet/api/microsoft.extensions.options.ivalidateoptions-1 'Microsoft\.Extensions\.Options\.IValidateOptions\`1')

### Remarks
A non\-positive limit takes the endpoints down rather than bounding them, and it does so differently on each
host: an MVC host answers 413 to every registration, including a valid one of a few hundred bytes, while a
minimal API host hands the value to a server that rejects it and answers 500\. Neither reads as a
configuration error at the point it surfaces, and both look to an operator like the endpoint being broken\.

Zero is refused alongside a negative value because it means the same thing here: a request body always
carries at least the two braces of an empty JSON object. A deployment that wants no bound of ours clears
the option instead, which this validator lets through.