Discover Top Posts Tagged with #pcre

Not responsible for the PCRE program frauds

Not responsible for the PCU program frauds

Not responsible for SNC & WE files

Not responsible for ARRIVESCAM frauds

Not responsible for the lack of respect for the Charter of Rights and Freedoms

Not responsible…

Everything blamed on Covid to keep us alive LOL with a 0.07% death rate LOL

Pas responsable des fraudes du programme PCRE

Pas responsable des fraudes du programme PCU

Pas responsable des dossiers SNC & WE

Pas responsable des fraudes d’ARRIVESCAM

Pas responsable du non respect de la charte des droits et libertés

Pas responsable…

Tout sur le dos du Covid pour nous maintenir vivant LOL avec un taux de 0.07% de décès LOL

#responsable #fraude #programme #PCRE #PCU #snclavalin #we #arrivecam #ArriveScam #charte #droitetliberté #responsible #fraud #program #charter #rightsandfreedom

First time looking at using a regex library in C.

Surprised and disappointed that neither the POSIX nor PCRE2 APIs have an out-of-the-box way to work on a FILE *.

I get that they would have to do their own potentially up-to-the-size-of-the-file memory allocation for matching in the worst case, and it's easier to just make the caller deal with that problem than to come up with a good API for dealing with all those problems...

..but clearly in many cases a string matching library is in a privileged position to

know how much to stream a file incrementally and how much still needs to be held in memory while checking for matches in the entire thing, and

heuristically know when it would be better to map the file into memory instead of streaming it.

Even if it weren't for the potential performance benefits, it's clearly a common use-case and makes a whole lot of sense as a developer convenience when so many things are files, and that's before we start to consider things like fmemopen, funopen/fopencookie, and fopen_memstream.

If only time were infinite... This is absolutely worth solving by either writing one's own regex-matching library and/or contributing to existing ones.

#software #software design #c #regex #pcre

bing crosby - paris holiday

-ax and ~PM~

#Wish You Were Here Wednesday #pcre

Answer: What are PCRE limits? #fix #answer #development

What are PCRE limits?

In ModSecurity there are PCRE limits exceeded errors.

I know I can fix this by setting rules such as:

SecPcreMatchLimit 150000 SecPcreMatchLimitRecursion 150000

But, what are these rules actually doing? What does the PCRE limit recursion set to 150,000 mean? What security holes am I allowing through by setting these so high? What does the recursion and limit mean?

I know…

View On WordPress

#mod-security #pcre #regex

e (PREG_REPLACE_EVAL) 警告この機能は PHP 5.5.0 で非推奨になります。この機能に頼らないことを強く推奨します。この非推奨の修飾子を設定すると、preg_replace() は、置換文字列において後方参照に関する通常の置換を行った後、 PHP コードとして評価し、検索文字列を置換するためにその結果を使用します。置換された後方参照においては、単引用符や二重引用符、バックスラッシュ (\)および NULL 文字はバックスラッシュでエスケープされます。警告マッチした後方参照ごとに addslashes() が実行されてから、置換を行います。つまり、クォートした文字列として後方参照を利用した場合、エスケープした文字がリテラルに変換されます。しかし、エスケープされた文字については、通常は変換されず、スラッシュが残ったままになります。そのため、この修飾子はとても複雑なものになってしまいます。警告 replacement が PHP のコードとして妥当な文字列であることを確認しましょう。そうでない場合は、 preg_replace() を含む行で PHP のパースエラーが発生します。警告この修飾子を使うことはおすすめしません。セキュリティに関する脆弱性を作ってしまいがちだからです。

PHP: 正規表現パターンに使用可能な修飾子 - Manual

#php #preg_replace #pcre #mariosnote

How-to: mod_security - PCRE limits exceeded #it #solution #answer

How-to: mod_security – PCRE limits exceeded #it #solution #answer

mod_security – PCRE limits exceeded

Just about on every request I am getting the following error:

Rule execution error - PCRE limits exceeded (-8): (null).

After a bunch of googling the only solutions seem to be

a) Add the following in your httpd.conf

SecPcreMatchLimit 150000 SecPcreMatchLimitRecursion 150000

b) Add the following to your php.ini

pcre.backtrack_limit = 10000000…

View On WordPress

#apache-2.2 #mod-security #pcre

Fixed: Non greedy regex matching in sed? #it #programming #answer

Non greedy regex matching in sed?

I’m trying to use sed to clean up lines of URLs to extract just the domain..

So from:

http://www.suepearson.co.uk/product/174/71/3816/

I want:

http://www.suepearson.co.uk/

(either with or without the trainling slash, it doesn’t matter)

I have tried:

sed 's|\(http:\/\/.*?\/\).*|\1|'

and (escaping the non greedy quantifier)

sed 's|\(http:\/\/.*\?\/\).*|\1|'

bu…

View On WordPress

#greedy #pcre #regex #regex-greedy #sed

How to: Non greedy regex matching in sed?

Non greedy regex matching in sed?

I’m trying to use sed to clean up lines of URLs to extract just the domain..

So from:

http://www.suepearson.co.uk/product/174/71/3816/

I want:

http://www.suepearson.co.uk/

(either with or without the trainling slash, it doesn’t matter)

I have tried:

sed 's|\(http:\/\/.*?\/\).*|\1|'

and (escaping the non greedy quantifier)

sed 's|\(http:\/\/.*\?\/\).*|\1|'

bu…

View On WordPress

#greedy #pcre #regex #regex-greedy #sed

#pcre

Trending Tags

Recently Viewed Tags

#pcre