Skip to content

Wrong detection of notification loops (due to new CB correlator management). #536

@mrutid

Description

@mrutid

Once in a loop we are generating this kind of correlators (due to new corr mangement at CB).

correlator":"b12cbfc2-e09f-11eb-9d80-0242ac110013; cbnotif=1; node=qVEyXINDl; perseocep=85962; cbnotif=1; cbnotif=1; cbnotif=1; cbnotif=1; cbnotif=1; cbnotif=1; cbnotif=1; cbnotif=1; cbnotif=1; cbnotif=1; cbnotif=1; cbnotif=1; cbnotif=1; cbnotif=1; cbnotif=1;

correlator = req.headers[constants.CORRELATOR_HEADER],

At PERSEO-FE we are using correlator to make loop detections:

correlator = req.headers[constants.CORRELATOR_HEADER]

Now it's not valid. We should remove "cbnotif=" atoms anddo the match just with "static part" os the correlator:

¿b12cbfc2-e09f-11eb-9d80-0242ac110013?
¿b12cbfc2-e09f-11eb-9d80-0242ac110013; node=qVEyXINDl; perseocep=85962?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions