/etc/apache2/conf.d/modsec_vendor_configs/OWASP3/util/regexp-assemble
##! Please refer to the documentation at ##! https://coreruleset.org/docs/development/regexp_assemble/. ##! The expression generated from this file matches a full HTTP ##! `Accept` header by following the specification as far as ##! necessary, while restricting the `charset` parameter ##! to a list of explicitly allowed values. ##! Where possible, the expression matches tokens "loosely", ##! to reduce complexity and the risk of false positives. ##! Specifications: ##! https://httpwg.org/specs/rfc7231.html#request.conneg ##! https://httpwg.org/specs/rfc7230.html ##! This is a duplicate of the 920600.data file. ##! There will be support for inclusion in the regexp_assemble tool in the future. ##! In the meantime, please keep both files in sync. ##!^ ^ ##!$ $ ##! Helpers ##!> template non-token-with-dquote-chars (),/:;<=>?![\x5c\]{} ##!> template non-token-chars \"{{non-token-with-dquote-chars}} ##!> template token-chars [^{{non-token-chars}}] ##!> template token-with-dquote-chars [^{{non-token-with-dquote-chars}}] ##!> template type-subtype (?:\*|{{token-chars}}+) ##!> template media-type {{type-subtype}}/{{type-subtype}} ##! list of allowed charsets ##!> assemble (?:"? ##!=> ##!> include allowed-charsets ##!=> \b"?)) ##!=< allowed-charsets ##!< ##! Main assembly ##!> assemble (?:{{media-type}}) ##!=> (?:\s*+;\s*+ ##!=> (?:(?:charset\s*+=\s*+ ##!=> ##!=> allowed-charsets ##! If the first part wasn't a "charset", then ##! anything is allowed here that is not "charset". ##! Note that this doesn't follow the RFC strictly. |(?: ##!=> [^c{{non-token-chars}}]{{token-chars}}* c[^h{{non-token-chars}}]{{token-chars}}* ch[^a{{non-token-chars}}]{{token-chars}}* cha[^r{{non-token-chars}}]{{token-chars}}* char[^s{{non-token-chars}}]{{token-chars}}* chars[^e{{non-token-chars}}]{{token-chars}}* charse[^t{{non-token-chars}}]{{token-chars}}* ##!=> )\s*+=\s*+{{token-with-dquote-chars}}+) ##! Clients like to violate the RFC, be lenient with ##! terminating semi-colons. ;? ##!=> )* ##!=> ##! Multiple "media-range" expressions can be ##! specified, comma separated. (?:\s*+,\s*+ ##!=> (?:{{media-type}}) ##!=> (?:\s*+;\s*+ ##!=> (?:(?:charset\s*+=\s*+ ##!=> ##!=> allowed-charsets |(?: ##!=> [^c{{non-token-chars}}]{{token-chars}}* c[^h{{non-token-chars}}]{{token-chars}}* ch[^a{{non-token-chars}}]{{token-chars}}* cha[^r{{non-token-chars}}]{{token-chars}}* char[^s{{non-token-chars}}]{{token-chars}}* chars[^e{{non-token-chars}}]{{token-chars}}* charse[^t{{non-token-chars}}]{{token-chars}}* ##!=> )\s*+=\s*+{{token-with-dquote-chars}}+) ##! Clients like to violate the RFC, be lenient with ##! terminating semi-colons. ;? ##!=> )*)* ##!=> ##!<
.
Edit
..
Edit
920600.data
Edit
921421.data
Edit
921422.data
Edit
922110.data
Edit
include
Edit
regexp-932100.txt
Edit
regexp-932105.txt
Edit
regexp-932106.txt
Edit
regexp-932110.txt
Edit
regexp-932115.txt
Edit
regexp-932130.data
Edit
regexp-932140.data
Edit
regexp-932150.txt
Edit
regexp-933131.data
Edit
regexp-933160.data
Edit
regexp-933161.data
Edit
regexp-934100.txt
Edit
regexp-941130.data
Edit
regexp-941160.data
Edit
regexp-942120.data
Edit
regexp-942130.data
Edit
regexp-942140.data
Edit
regexp-942150.data
Edit
regexp-942170.data
Edit
regexp-942180.data
Edit
regexp-942190.data
Edit
regexp-942200.data
Edit
regexp-942210.data
Edit
regexp-942240.data
Edit
regexp-942260.data
Edit
regexp-942280.data
Edit
regexp-942300.data
Edit
regexp-942310.data
Edit
regexp-942320.data
Edit
regexp-942330.data
Edit
regexp-942340.data
Edit
regexp-942350.data
Edit
regexp-942360.data
Edit
regexp-942370.data
Edit
regexp-942380.data
Edit
regexp-942390.data
Edit
regexp-942400.data
Edit
regexp-942410.data
Edit
regexp-942470.data
Edit
regexp-942480.data
Edit
regexp-assemble-v2.pl
Edit
regexp-assemble.pl
Edit
regexp-cmdline.py
Edit