HTML Purifier VS FluentValidation

HTML Purifier

On the homepage of http://htmlpurifier.org the last update is of december 2021. I didn’t think of checking GitHub. Thanks for the info!

For HTML specifically, HTMLPurifier is pretty well known.

There are several third party PHP libraries which are commonly used to assist in XSS prevention. Examples👇 HTML Purifier – here PHP Anti-XSS – here htmLawed – here

You need to filter the received HTML code and remove the tags and attributes you don't allow. The easiest way to do this is to use htmlpurifier. Otherwise you have to manually cleanup the HTML by using strip_tags and maybe some xml parsing (or regex) to remove unwanted attributes.

Or HTMLPurifier.

Definitely, its one of the best http://htmlpurifier.org/

Popular Packages & Tools - The League of Extraordinary Packages - Twig Templating engine - PHP Mailer - SwiftMailer - Flysystem file storage - PHPUnit testing - HTML Purifier

Check out this lib: http://htmlpurifier.org/. It is widely used in the PHP World.

Here is an example of Command handler with built-in Fluent Validation and fire and forget style:

There is an RFC called Problem Details (RFC7807) that standardizes how an error in an API should be responded to for the client. If you use Fluent validation, you may have noticed that the response is within this pattern.

here we're defining the input validation requirements using fluent validation rules. let's see what happens when the user input doesn't meet the above criteria. execute the same request in swagger with the following incorrect json content:

I remember FluentValidation being a nice library for this type of stuff.

Literally the code example in the front page: https://fluentvalidation.net/

https://www.nuget.org/packages/Newtonsoft.Json/ https://www.nuget.org/packages/AutoMapper/ https://www.nuget.org/packages/Dapper/ https://www.nuget.org/packages/FluentValidation/ https://www.nuget.org/packages/FluentAssertions/ https://www.nuget.org/packages/NUnit/ https://www.nuget.org/packages/xunit/ https://www.nuget.org/packages/YamlDotNet/ https://www.nuget.org/packages/Moq/ That is simply not true. Mature c# projects purposely maintain no downstream dependencies and is they do, it's to a major reputable lib. See for yourself - these are staple third party packages commonly used. Anything dependency starting with System or NETStandard is Microsoft maintained.

FluentValidator for validating and authorising certain fields.

Now that we know the importance of providing users with enough information about their requests and how it was processed, let’s focus on how we can configure our API to help us do that.One aspect of such meaningful experience is Request Validation (400 Error Range). For that purpose I am using a library called Fluent Validation.