|
If you were logged in you would be able to see more operations.
|
|
|
| Resolution Date: |
12/Jun/05 10:14 PM
|
|
The Filter api currently assumes that it would be applied only on unopened sessions. Eg - the SSL filter currently starts its work on the sessionOpened() callback. This is an incorrect assumption since the SSL filter could be applied on an existing plain TCP connection as well.
It would be great if there were new callbacks defined - something like filterEnabled() and filterDisabled()
This would allow us to use the filters on existing sessions as well.
|
|
Description
|
The Filter api currently assumes that it would be applied only on unopened sessions. Eg - the SSL filter currently starts its work on the sessionOpened() callback. This is an incorrect assumption since the SSL filter could be applied on an existing plain TCP connection as well.
It would be great if there were new callbacks defined - something like filterEnabled() and filterDisabled()
This would allow us to use the filters on existing sessions as well. |
Show » |
made changes - 17/May/05 02:37 PM
| Field |
Original Value |
New Value |
|
Status
|
Open
[ 1
]
|
In Progress
[ 3
]
|
made changes - 23/May/05 03:11 PM
|
Fix Version/s
|
|
0.9
[ 11069
]
|
made changes - 12/Jun/05 10:14 PM
|
Status
|
In Progress
[ 3
]
|
Resolved
[ 5
]
|
|
Resolution
|
|
Fixed
[ 1
]
|
made changes - 05/Jul/05 02:53 PM
|
Status
|
Resolved
[ 5
]
|
Closed
[ 6
]
|
|
Improvement
Closed
Blocker
Filter API needs callback for enabled notification
