Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
mrutid opened this issue Jul 9, 2021 · 2 comments
Closed

Comments

@mrutid
Copy link
Member

mrutid commented Jul 9, 2021

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?

@AlvaroVega
Copy link
Member

related #457

@fgalan
Copy link
Member

fgalan commented Jul 23, 2021

PR #537

Should this issue be closed once that PR has been merged?

@fgalan fgalan closed this as completed Aug 5, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants