Loading...

XML

Word

Printable

Type: Problem report
Resolution: Fixed
Priority: Critical
Fix Version/s: 3.4.0alpha1, 3.4 (plan)
Affects Version/s: None
Component/s: Agent (G), Proxy (P), Server (S)
Labels:
- pcre
- regexps

Sprint:
Sprint 4, Sprint 5, Sprint 6, Sprint 7, Sprint 8
Story Points:
4

zabbix frontend uses perl regexps, server - posix extended.
on the frontend, posix-e is deprecated since 5.3.0 (according to http://www.php.net/manual/en/intro.regex.php)

this is bad because of inconsistency, but especially bad for cases when both frontend and server are supposed to do the same thing, for example, global regexps (testing in frontend and actual use in server)

keywords : pcre

note that this concerns all daemons, not just server - proxy, agent and java gateway should be verified, too

causes

ZBX-13031 Zabbix Java gateway cannot compile without libpcre

Closed

ZBX-13192 GNU regular expressions still mentioned in documentation

Closed

is duplicated by

ZBXNEXT-2537 Support Negative Lookahead

Closed

ZBXNEXT-968 multiline regular expression matching

Closed

ZBX-5021 Regular Expressions for web.page.regex returning unexpected results

Closed

ZBX-10689 Different regexp libraries in use in Frontend and Backend.

Closed

ZBX-13365 Regular expression isn't evaluated correctly in trigger context

Closed

ZBX-10920 regexp included '\t' does not work properly

Closed

ZBX-11779 Wierd behaviour of regsub on ITEM depending on context

Closed

ZBX-8789 Test regexp passed with extended syntax, not only POSIX syntax

Closed

(5 is duplicated by)

Assignee:: Vladislavs Sokurenko

Reporter:: richlv

Team:: Team C

Votes:: 20 Vote for this issue

Watchers:: 22 Start watching this issue

Created:: 2011 Jul 06 17:02

Updated:: 2024 Apr 10 17:19

Resolved:: 2017 May 31 11:21

Details

Description

Attachments

Issue Links

Activity

People

Dates