Skip to content
This repository has been archived by the owner on Dec 14, 2018. It is now read-only.

Possible double-execution of filter providers #4504

Closed
rynowak opened this issue Apr 19, 2016 · 0 comments
Closed

Possible double-execution of filter providers #4504

rynowak opened this issue Apr 19, 2016 · 0 comments
Assignees
@kichalla
Labels
3 - Done bug
Milestone
1.0.0

Comments

@rynowak
Copy link
Member

rynowak commented Apr 19, 2016

We're seeing a filter provider called twice per-request in an orchard scenario

Stacks:

1

2
@Eilon Eilon added this to the 1.0.0 milestone Apr 19, 2016
kichalla added a commit that referenced this issue Apr 21, 2016
@kichalla
Filters provided by filter providers are made to never be cached
3de86f9 
[Fixes #4504] Possible double-execution of filter providers
kichalla added a commit that referenced this issue Apr 21, 2016
@kichalla
Filters provided by filter providers are made to never be cached
47013e5 
[Fixes #4504] Possible double-execution of filter providers
@kichalla kichalla mentioned this issue Apr 21, 2016
Closed
kichalla added a commit that referenced this issue Apr 21, 2016
@kichalla
Filters provided by filter providers are made to never be cached
2daa784 
[Fixes #4504] Possible double-execution of filter providers
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@kichalla kichalla

Labels
3 - Done bug
Projects
None yet
Milestone
1.0.0
Development

No branches or pull requests
3 participants
@Eilon @rynowak @kichalla