[MAGNOLIA-3858] Support for multiple HttpClientCallback, where the callback itself decides if it handles the request Created: 12/Oct/11 Updated: 25/Apr/12 Resolved: 02/Nov/11 |
|
| Status: | Closed |
| Project: | Magnolia |
| Component/s: | security |
| Affects Version/s: | None |
| Fix Version/s: | 4.5 |
| Type: | New Feature | Priority: | Major |
| Reporter: | Magnolia International | Assignee: | Magnolia International |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Template: |
|
||||||||||||||||||||||||
| Acceptance criteria: |
Empty
|
||||||||||||||||||||||||
| Description |
|
Improve the HttpClientCallback security mechanism, so that multiple callback implementations can be registered by default, and each callback can "decide" if they'll handle the request or not. This should allow implementations for different types of clients to intercept a request, based on other criteria than the request's path. Described here: http://wiki.magnolia-cms.com/display/DEV/Support+multiple+HttpClientCallback+by+default |
| Comments |
| Comment by Magnolia International [ 02/Nov/11 ] |
|
See |